Winter 2005

Welcome to issue #30 of Profiles Magazine! Regular readers will notice that the web site sports a brand-new look and feel. We've redesigned the site to freshen it but more importantly, to make it easier for you to find the information you need. In the coming months, we will introduce additional services and features that we hope you'll find useful.

We call upon the talented Ron Grabau of HP for this month's cover story on user-defined features. Ron discusses how to employ UDFs to get better productivity and consistency from your designs. Additionally, there is a full complement of tips and news that you don't want to miss.

In the meantime, feel free to share your praise or criticisms about the magazine with us. You can write me at [email protected].

Best Regards,

Rick Snider

Creating Pro/ENGINEER Geometry with User-Defined Featuresby Ronald Grabau, HP

Managing Changeby Evan Caille, PTC/USER President

PTC/USER and RUGs Put Users Firstby Ed Stevenson, Director of Regional User Groups

Effective Large-Scale Distribution of Wildfire and Other Large Toolsby Israel Pabon, Raytheon

Going Native—Finding Qualified Pro/ENGINEER Partnersby Greg Saisselin, ProeSuppliers.com

http://www.profilesmagazine.com/index.html

http://www.profilesmagazine.com/tips.html

http://www.profilesmagazine.com/past.html

http://www.profilesmagazine.com/contacts.html

mailto:[email protected]

Regional User Group Calendar

Download a PDF of this issue

Copyright 2005 PTC/USER, Inc. All rights reserved.

Changing the Order of "Save a Copy" File Typesby Greg Kemner, Northrop Grumman–Cutting Edge Optronics

Another Take on Decalsby Jason Baggett, Rheem Manufacturing Co. A/C Division

How to Update the Drawing System Parameter &todays_date Before Printingby Ceferino Sanchez, ASTEC Power, a Division of Emerson Network Power

Easy Axis Justificationby Steve Regsiter, General Atomics Aeronautical Systems

http://www.profilesmagazine.com/p30/members.ptcuser.org

http://www.profilesmagazine.com/copyright.html

Creating Pro/ENGINEER Geometry with User Defined Featuresby Ronald Grabau, HP

User Defined Features or UDFs provide a fast, flexible, and accurate way to reproduce Pro/ENGINEER geometry. When you define a UDF, a .gph file is created that contains all the information necessary to copy the desired geometry. UDFs can be made of any Pro/ENGINEER geometry, including assembly features and component assembly. By using the UDF instead of manually placing the geometry, you also assure better productivity and consistency.

Figure 1

Creating the Geometry

The first step is to create the geometry you want to copy. There is no real magic here but there are a few useful tips to get you started in the right direction.

● Reference control is a must. The two basic rules when creating your geometry are that the UDF (1) needs to prompt for all references used, and (2) recognizes if a parent is used multiple times.

● Create a simplified model of all the geometry. ● Create a point or axis before you start creating the geometry that will be in the

UDF. Use this feature as the primary reference for all features that go into the UDF.

● Delete all references from the sketch. Add the locating point or axis as a reference and use centerlines for horizontal and vertical references.

● Consider how these features will be used in other parts. Will they always be on a flat plane? What references will be required? Will a hole work better than a cut?

Creating Pro/ENGINEER Geometry with User-Defined Features

Managing Change

PTC/USER and RUGs Put Users First

Effective Large-Scale Distribution of Wildfire and Other Large Tools

Going Native—Finding Qualified Pro/ENGINEER Partners

Changing the Order of "Save a Copy" File Types

Another Take on Decals

How to Update the Drawing System Parameter &todays_date Before Printing

Easy Axis Justification





The features you use may determine how robust your UDF is. ● No reference prompt is necessary when you are referencing geometry that is

within the UDF definition. ● When scaling geometry is an option, model the geometry so that there is a

primary dimension with a value of 1. This makes scaling factors easy. ● Driving geometry with parameters and relations should be no problem. For

relations that use parameters, use feature relations. An extra regeneration after placing the UDF will be required for feature relations. Relations don't work if you use dimensions that are not part of the UDF geometry.

● Resize datum planes if they are included with the UDF. A hidden datum will not remain hidden after the UDF placement.

Creating the UDF

It’s important to start with a clear understanding of what you want to achieve. I recommend creating a short checklist so that you will know what options you want to use. Here are some examples from my own checklist.

● What am I trying to accomplish? ● How will the geometry vary (specific sizes, infinite sized, predefined or user-

defined dimensions)? ● What are the driving features? ● Is my geometry created correctly to get the desired results? ● What references are going to be required?

The UDF creation option is found under Tools>UDF Library>Create. To begin the process, you must define the following series of required and optional features.

Required Features

UDF Name. The first prompt will be for the UDF name. This name will be appended with the .gph extension.

UDF Options. These options ask if you want a reference model. The reference model will be used when you are placing the UDF. Any references will be highlighted in this model, clarifying what is being asked for in the reference prompt. The options are:

Stand Alone

● The reference model is optional (answer Yes or No). ● If a reference model is used, the current model will be copied. You also have an

option to display the reference model or not when the UDF is used. ● If a reference model is not used, there will be no prompt for one.

Subordinate

● The current model is used for the reference model. ● The reference model is always displayed when placing the UDF.

Tip: I recommend the subordinate option. The reason is that if you ever need to make changes to the UDF geometry, a reference model will be required. If you don’t have one, you may be forced to start the UDF creation from scratch.

Figure 2

Adding the Geometry to the UDF. During this prompt, you will add the geometry to the UDF. Here are my suggestions:

● Choose only the features that make up the desired geometry. ● Do not select “reference” or parent geometry. ● Use any normal selection method (Pick from Model, Pick from Model Tree, By

Layer, Range).

Reference Prompts. After picking all your geometry, you now need to enter prompts for all the references. Remember I mentioned that minimizing references is important? Well, this is where you find out how good a job you’ve done. Most of my UDFs have three to four prompts—typically a sketch plane, an orientation plane, and a location prompt.

Tip: I can tell you from experience that having too many prompts makes the UDF more confusing than useful. If you have too many prompts, try changing the geometry to reduce references.

Figure 3

● Every reference needs a textual prompt. ● Prompts appear in the message window. ● A good prompt directs the user to select the correct reference. ● Be clear and concise. Long descriptions may confuse more than help. ● Be consistent in your wording. ● Pro/ENGINEER automatically adds the text “Select” as the first word to the

message prompt. ● When a reference is used more than once, you have two options on how to

proceed: (1) Single—you will be prompted only once for the reference, or (2) Multiple—you will have to select the reference every time it is needed.

Tip: I generally recommend a single prompt.

Figure 4

● At the end of the prompts, you can cycle back and make changes before proceeding.

Options for Adding Variables

Variable Elements. This option lets you edit the definition of a feature when the UDF is placed. All you need to do is select the feature that will vary. When this feature is created by the UDF, the user is automatically placed into the feature definition where changes can be made.

Variable Dimensions. If you pick a dimension from the features in the UDF, a prompt for that dimension will be required and the user will input a value when placing the UDF.

Dim Values. This allows you to edit any existing values in the reference part. Use this if you find that the current size or shape is incorrect and you want to change it without exiting the UDF definition.

Units. With this option you can change the base units of the UDF the same way you would change the units of a part. Having the correct units can avoid some extra steps when placing the UDF. If the units between the UDF and receiving model differ, there is a placement option to correct this.

Ext Symbols. This option lets you assign parameters used in relations to parameters in the receiving part.

Family Tables. Like “normal” family tables, this option provides a method for adding variable dimensions and features. Note that:

● There is no verification of instances. ● Unique instance names between different UDFs are not required. ● Placed geometry is not an instance. ● No family table relationships exist after the geometry is created.

Tip: Layers and surface colors do not transfer when you use a UDF.

Figure 5

Using the UDF

Now it’s time to choose the options as you place the UDF. To place a UDF, go to Insert>User Defined Feature.

Reference Model. In the definition, you had an option for Stand Alone or Subordinate. If you used Stand Alone but said yes to the reference model, the first prompt will ask if you want the reference part. Yes brings the reference part up in a sub window, No moves you to the next option without a reference model. The reference model pops up within a sub-window.

Figure 6

Placement OPTS. You have two choices:

● Independent places the UDF geometry in the current model just as if you created all the geometry manually. Dimensions for features can be Normal, Read Only, or Blanked.

● UDF Driven geometry placed with this option will be driven by the UDF. This means you must make modifications to the UDF to change the geometry. Changing the UDF changes all geometry in all models using this option.. Dimensions can be Read Only or Blanked.

Tip: I recommend Independent. This allows individual changes to the geometry and avoids dependency to the UDF. If you have a dependency to a UDF, all instances of that UDF will be modified when you change the UDF.

Scale. This next prompt is for scaling options. With these options, it doesn’t matter if your UDF has the same units as the receiving part. If the UDF and part are the same units, the Same Size option will not be available.

● Same Size converts geometry to a different unit without changing the size of the geometry (1 inch becomes 25.4 mm).

● Sam Dims uses the current dimensions or converts the current dimensions to a different unit (1 inch becomes 1 mm).

● User Scale scales the geometry by a user input value.

Dimension Display Options. Display options apply rules to dimensions that have not been designated as variable. Here are the choices:

● Normal shows all dimensions and allows modifications. Use this option when you may need to change some geometry later.

● Read Only lets you see but not modify the dimensions. This is a good choice for documentation.

● Blank doesn’t let you see or change any dimensions. Choose this option for company logos or features that you don’t want modified.

Figure 7

Selecting Your References. For the features that require references, you will be prompted for the new references. This is where the reference model comes in handy. For

each prompt, the reference model highlights what was used on the original model. The message prompts you typed in for each reference will be displayed in the message window.

Directional Arrows. Directional arrows are only displayed if the orientation of a feature is ambiguous. (This happens when you use datums for orientation because there are two sides to each datum.) Changing the arrow direction changes the orientation of the feature(s).

Figure 8

Finalizing the UDF

Before you finish your UDF, you can use the Group Placement menu to change many of the options. This way, you don’t have to start all over if you made a mistake. When redefining, you have the following subset of options:

● Scale lets you redo the scaling options. ● Var Dims lets you change an incorrect value. ● Dim Display lets you reset the display of non-variable dimensions. ● References lets you redo the references. ● Reference Action lets you flip the directional arrows.

Figure 9-1 Figure 9-2

Examples of User Defined Features

Most of my UDFs fall into one of three general categories—Standard, Variable Dimension, and Scalable. These categories help me understand some of the

requirements for my checklist. Here are simple examples of each type.

1. Standard UDF: Staking Feature

Standard UDFs are those that “just copy the features” and have no special requirements or options. They may, however, contain a UDF family table. In this example, the UDF only has two features but is used a lot and has standard dimensions to meet a company specification.

Feature Creation

● Base feature is the square protrusion. This is not part of the UDF. ● Axis is placed in the middle of the part and used as the locating reference. ● A protrusion is placed using the axis and top surface. ● A coaxial hole is created using the placement axis and the same surface as the

form placement. The hole definition is a two-sided hole using the To Next depth option.

UDF Creation

● Subordinate (will have reference model) ● Two features (protrusion for cylinder and hole) ● Prompt: Select locating axis ● Prompt: Select surface for protrusion ● Family table (allows users to pick predetermined heights)

2. Variable Dimension UDF: Snap Feature

A Variable Dimension UDF is the same as the standard except that you have to enter selected dimension values. In this example, the snap feature varies only in height.

Feature Creation

● Base feature is the square protrusion and datum point for feature location.

● The first feature for the UDF is the rectangle protrusion. Since the snap may go on non-planar surfaces, I made a datum plane offset a height from the point and then used the To Next depth option.

● The rest of the features are created referencing only the rectangle protrusion or locating point.

UDF Creation

● Subordinate (will have reference model) ● Six features

● Variable dimension is the offset datum plane dimension ● Prompt: Select locating point ● Prompt: Select sketch plane reference (plane that the snap will be normal to) ● Prompt: Select sketch plane orientation ● Prompt: Enter snap height

UDF Placement

The user is prompted for three references and one value input. The PNT0 is used for the locating point, the Top Datum plane for the sketch plane references, and the front of the part for the sketch plane orientation.

Since a datum plane is used for the sketch plane reference, the reference direction must be specified. In this case, the arrow is pointing in the direction we want the snap to be built.

The finished snap takes only seconds to create.

3. Scalable UDF: Company Logo

A Scalable UDF applies a user-defined scale to the geometry. This is a good solution for a company logo, which has infinite sizes and geometry that is too complex to just modify the dimensions.

Feature Creation

● Note the dimensions. To allow easy scaling, the entire logo is scaled so that the width dimension is 1.

● The two centerlines are aligned with the locating point. ● Since the geometry is placed on any type of surface, I used the Offset feature.

UDF Creation

● Just create a standard UDF.

UDF Placement

● When asked for the scale, use the User Scale option. Enter the size of the logo as desired.

● For the Dim Display, I use Blank since there is no good reason to display the dimensions.

● When you get to the preview, see if the geometry is correct. If the logo is backwards, use Redefine to change the references or the Regen Action.

Figure 20-1 Figure 20-2

Once everything is set, finish the feature creation. Again, an otherwise difficult task for most Pro/ENGINEER users takes only seconds with a UDF.

Conclusions

While User Defined Features are not the only method for copying or creating geometry in Pro/ENGINEER, they do provide capabilities that are not found in other options. Where repeatability, consistency in modeling and efficiency are important, consider using a UDF. Here’s a quick recap of benefits.

Enables users to copy features from one model to another.

Offers options not found in other top-down design tools, including:

● Prompts ● Family tables ● Relation copy ● User input ● Parameter selection ● Scalability

Generates productivity gains:

● Commonly used features are easily created ● Creation methods are consistent ● Can be used as “start” geometry and modified as necessary ● Assures correct geometry ● Geometry is created quickly and accurately by new as well as experienced users.

Where to Get Help

Go to the Help Center at www.ptc.com. Under Part Modeling, there is an entire section devoted to UDF features and groups.

Ronald B. Grabau is a MCAE engineer at HP in Houston, Texas, USA. He can be reached by email at [email protected].

http://www.ptc.com/

Managing Changeby Evan Caille, President of PTC/USER

As a student of both history and science, I’ve always been fascinated by the people and stories behind the creation, adoption, and eventual obsolescence of technology. It’s really true that history repeats itself. Delve into the stories behind invention of the typewriter, the computer, and the Internet, and you’ll discover a similar pattern—the technology initially meets with rejection and skepticism, gradually gains grudging acceptance, and ultimately becomes a ubiquitous part of our lives.

In some cases we embrace the change, while at other times we loathe it. Sometimes we do both at once. For example, I often wonder how we ever conducted business without the benefit of e-mail, while also grumbling about the amount of spam in my inbox. Like it or not, technological shifts affect our lives at home, at work, and at play.

And the pace of change is increasing, with new technologies being introduced and abandoned as never before. Consider the VCR. A recent article (http://www.physorg.com/news2099.html) reports that a major retail chain in the UK will no longer sell them, given that sales of DVD players now outstrip sales of VCRs by a factor of 40 to 1. And this comes a mere 26 years after the VCR first appeared on the market.

Within this fast-paced environment, manufacturing organizations typically embrace the concept of continuous process improvement as a way to develop better products while also decreasing time-to-market. These process changes often involve introducing new tools or upgrading old ones. With each change, there is usually a short-term productivity hit until the new tool or process has been fully assimilated. Thoughtful and justified change is painful, but the long-term benefits are immense.

Just consider what’s happened with Pro/ENGINEER. In the 18 years that it’s been on the market, the software has undergone major overhauls to both the very visible user interface and the less apparent “under-the-hood” modeling engine. The user interface changes, in particular, have caused consternation for some because they force us to change how we use the tool and briefly take us out of our comfort zone. For users who have made the transition to Wildfire and now to Wildfire 2.0, I’m sure the experience has been equally disruptive. It’s like replacing your hammer with an electric nail gun when you’re framing a house. The nail gun is vastly more efficient but it takes some getting used to just because it is so different. We have to get beyond the hurdle of simply pounding on a nail with the nail gun turned off because “that’s the way we’ve always done it.”

This is where the PTC and PTC/USER partnership comes into play. Our common goal is to ensure that users of Pro/ENGINEER and Windchill products are able to realize maximum value from their investment. Together we provide a full range of services to help both new and experienced users attain, and maintain, proficiency on PTC’s


Managing Change












http://www.physorg.com/news2099.html

http://www.physorg.com/news2099.html

software products. Through our Technical Committees, Regional User Groups, annual conferences, educational offerings, and newsletters, PTC/USER provides opportunities to gain valuable knowledge and interact with PTC on a variety of levels. For example, PTC conducted Pro/ENGINEER Wildfire update training at the last two PTC/USER conferences in North America.

By the way, productivity improvement is a good selling point to make to your management when trying to justify attendance at the next PTC/USER World Event. Taking this opportunity to attend expert presentations, meet with PTC product managers, visit industry partner booths, and interact with your peers all in one venue is a cost-effective way to learn practical ideas to help you extract the full potential from the tools we employ. I personally have not left a single PTC/USER conference without at least three or four significant tips that could be immediately implemented at my company to improve our users’ productivity. This is in addition to all the other knowledge gained that helps with the long-range planning and day-to-day operation of our CAD and PDM systems. The small investment in the conference fee and travel costs pays off several-fold, yielding a good return for your company.

The pace of technological change is not slowing down. As PTC products continue to evolve, you will need to tap into every resource to keep up with the advances. PTC/USER, in partnership with PTC, is committed to providing you with valuable and practical knowledge to assist you in this endeavor. Don’t become obsolete. Become a PTC/USER member, become engaged, and reap the benefits.

Evan Caille works at HP in Houston, TX. He can be reached via e-mail at [email protected].


PTC/USER and the RUGs are Putting Users Firstby Ed Stevenson, Director of Regional User Groups

Over the past year and a half, PTC/USER has been working hard to develop more effective ways to support the 70+ Regional User Groups (RUGs) operating around the world. RUGs are independently run organizations formed by PTC software users in a particular community or geographical area.

In my role as a PTC/USER director, I’ve discovered that most Regional User Group leaders struggle with the same issue—how do I take my group to the next level by developing better presentations, better forums, better Industry Partner relationships? To assemble and articulate the best methods for achieving these goals, PTC/USER has launched the User First Initiative—a collaborative program to advance our shared mission of promoting information exchange among PTC product users.

Regional User Group chairs from around the world participate in our annual Leadership Forum to discuss common challenges and solutions.

Members of the advisory council leading the User First Initiative represent a wide selection of Regional User Group representatives: Adam Bush (Southwestern Michigan), Mike Dolan (Northern Ohio), Ron Fridell (Oregon), Carrie Ives (North Texas), and Craig Shott (Tucson, Arizona). Also participating are Kelly Blomquist of PTC and Trish Hudson of the Center for Excellence in Association Leadership (CEAL).


Managing Change








More information about RUGs is available at our web site...





http://www.cealweb.com/

http://members.ptcuser.org/Resource.phx/rug/rug.htx

CEAL develops new and innovative programs, products and services to strengthen the effectiveness of volunteer and staff leadership teams. I thank them for their dedication in adding the advisory council responsibility to their already heavy workloads.

What does the User First Initiative hope to accomplish?

User First is about bringing the resources and power of PTC, PTC/USER and the RUGs directly to every PTC customer regardless of industry, location, job description, or skill level. In essence, our aim is for each and every PTC product user to have a local group available for education, information exchange, and support.

To achieve this ambitious goal, we are defining a more formal relationship between PTC/USER and the RUGs. The objective is to develop a consistent and well-documented process that will allow the RUGs to place PTC customers first, and PTC/USER to place the RUGs first. What this means is that PTC/USER will provide broad support to enable RUG leaders to focus their energies on meeting the needs of their members rather than on securing resources and other short-term demands. For their part, RUG participants will have a higher-quality, more consistent experience.

If we can eliminate wasted effort, we can do more with less or more with at least the same amount of time. We have learned, for example, that when the RUG chairs actively pursue the involvement of companies in the area, the level of participation and quality of meetings improve. What this comes down to is that users leave the RUG with more and better Information. The more we optimize the exchange of information, the more value both companies and individuals will find in participating.

What changes has PTC/USER made so far?

In the first round of changes, we’ve constructed a relationship framework that details what RUGs do and what PTC/USER does. This clarity should free up time and ease some of the pressures on the RUG chairs in managing daily operations. We have also implemented a number of infrastructure improvements to facilitate communications among the RUGs, including a community web page that allows members to browse meeting calendars and register for upcoming events.

Our current efforts are going toward assembling a comprehensive resource manual to help RUG leaders set their groups up for success. This document will establish criteria for Regional User Groups that want the support of PTC/USER, including minimum number of meetings per year, costs, and other operational details. Existing RUGs are now in the process of reviewing and commenting on the basic outline of these new rules and responsibilities.

Why should PTC customers get involved with a RUG?

Companies are realizing that it takes more than great tools to develop great products. They need what PTC calls a Product Development System (PDS) that is tuned to their company. A PDS comprises several components that run smoothly together. The competitive advantage now becomes a matter of who can get more with less—less people, less software, and less time.

Meanwhile, sales forces are aggressively selling “solutions” into companies. It is easy to become confused by the alternatives or to overlook options when attempting to pick approaches, people, and processes. Employees have a real need for a neutral forum in which to exchange information. While PTC/USER fulfills that mission on a global scale, users need a similar forum located within a reasonable distance and available at a

reasonable cost. Regional User Groups offer a relatively inexpensive alternative/complement to other training modes.

Active participation in RUGs has optimal value—a local, inexpensive forum where real, unfiltered information flows freely. Users receive broad exposure to creative approaches within the software. For example, learning how one company quickly creates toys can help another company learn how to make medical equipment, which helps another company make defense equipment. From personal experience, I can say that I’ve always learned something at every a RUG meeting I’ve attended, and I’ve always left feeling it was worth the time and expense.

What role do PTC/USER’s Industry Partners play within the RUGs?

Today companies that make products that complement PTC software need efficient, cost-effective ways to market themselves to PTC users. PTC/USER’s Industry Partners Program is second to none in providing this broad reach.

What’s more, Regional User Group meetings provide the best forum imaginable for industry partners and value-added resellers. A local meeting might have 50, 100 or sometimes more than 200 PTC product users gathered in one place. As PTC product users are putting together or implementing a company’s Product Development System, this exposure to technology can be invaluable. This is a win for everyone—the industry partner companies get exposure, users learn about new technologies and tools, and the RUG itself has an opportunity to bring in revenue from participating vendors to pay for the cost of the meeting.

Why should I lead a RUG?

Some people become RUG leaders because it “looks good on resume,” while others do it because they like to lead. Still others do it as part of their employment. In my own case, I needed help and couldn’t get it from any other source. That quickly evolved into my being able to help others, which I find personally as well as professionally rewarding. If you surveyed our current RUG leaders, I think you would find the desire to help others is a motivation for many.

As a person who has been involved in forming many RUGs, I can say that the experience has proven to be a great way to meet people. I’ve met most of my professional friends through user group interactions. This exposure has given me a Rolodex full of contacts that I can call any time for perspectives, answers, or just sympathy.

In addition, running a RUG offers unique access to PTC’s senior decision makers. Each quarter, RUG leaders participate in conference calls with PTC senior managers—a rare chance to ask direct questions and receive candid answers about what’s happening with PTC software. RUG leadership also provides great opportunities to build professional skills in public speaking, management, leadership, and business communications. And last but not least, RUG chairs receive fee discounts for PTC/USER World Events.

How do I start a Regional User Group?

Generally you should find at least three people who really want to have a vibrant RUG in your area and are willing to make a two-year commitment to make it happen. Once you’re got your team in place, just contact me to request a RUG “starter kit” to help you get up and running. In addition to myself, several other members of the PTC/USER board and staff have experience running Regional User Groups and are available to help. With your hard work and our support, you will be successful.

If you have any questions or comments about Regional User Groups, I welcome your comments and feedback at [email protected]. With your participation, we can make the User First Initiative a reality for all PTC product users.

Ed Stevenson is Director of Regional User Groups for PTC/USER. He currently works at Pelco in Clovis, CA.


Effective Large-Scale Distribution of Wildfire and Other Large Toolsby Israel Pabón, Raytheon Your typical default Pro/ENGINEER Wildfire 2.0 and Pro/INTRALINK 3.3 installation takes anywhere from 800Mb to 1Gb of space, depending on selected options. If you have only a couple of workstations to update, you might be able to update one at a time. If you want to use your time better, you can use a simple command line script to perform a serial XCOPY process via a network to automate and simplify the process. But what happens when you have hundreds of workstations to update?

Quality distribution of software application packages to multiple users is a challenging and demanding task. Delivering such tools with close to zero errors is the goal. Is it a nearly impossible task? Not if you learn to harvest the power of MS Windows Server 2003 Policies and Active Directory. In this article you will learn how to distribute a software tool image (such as a Pro/ENGINEER Wildfire and Pro/INTRALINK package) in a short period of time with minimum negative impact. Using this approach to large-scale application distribution will help you keep downtime to a minimum.

Server Policies Approach

Before you even begin working with the Server Policies, you must first create and identify a quality build to package. Start with at least a basic list of operations that are critical to you and to verify them using any given build or release of the tool. You don’t need a Q/A department—only a clear understanding of what the minimum quality level should be and that the application meets it. Once you have selected the best possible version of the product, you can decide how to package it for distribution.

Packaging an application can be as simple as creating a self-extracting zip file that will decompress all image files in the default preferred path. You can use such tools as WinZip (www.winzip.com) or WinRAR (www.rarlabs.com) for this. You can also use more complex install tools such as Install Shield (www.installshield.com) to prepare detailed deployment images. These packages offer much more flexibility on what to do with the applications.

What are Server Group Policies? They are an administrative feature in Windows Server 2003 that automate tasks by creating actions (or policies) that will be applied to a given group of users. They allow both minimal intervention and a high level of control.

A note of warning: Only administrators can use Group Policies to restrict or allow access to specific tasks. This applies in a network where Group Policy has been configured using Active Directory. (For more information, search for Active Directories and Group Policies at the Microsoft website www.microsoft.com/windowsserver2003/).


Managing Change












http://www.winzip.com/

http://www.rarlabs.com/

http://www.installshield.com/

http://www.microsoft.com/windowsserver2003/

Distribution Process

In the following example, we’re going to distribute an MSI image. The MSI file contains the distribution image of applications we tested and will place such applications at a predefined target location in each user’s workstation. (Note: There are different tools to create MSI files. Check Install Shield’s “Package for the Web” tool at http://www.installshield.com/downloads. While it doesn’t matter which one you use, keep in mind that this is the preferred method for Microsoft applications.)

1. Download and install the Group Policy Management Console with Service Pack 1 from Microsoft at http://download.microsoft.com/download/a/d/b/adb5177d-01a7-4f04-bfcc-cb7cea8b5bb7/gpmc.msi

Figure 1

2. After installation, launch the application from the start Menu >Programs > Administrative Tools. Look for Group Policy Management.

Figure 2

3. Note that the Group Policy Management dialog has a typical tree structure where your active directory forest is displayed at the top level. If available, look for your domain and then your proper group or organization unit. Right-click the object you want to deploy software to and then click Create and Link GPO Here.

http://www.installshield.com/downloads

http://www.installshield.com/downloads

http://download.microsoft.com/download/a/d/b/adb5177d-01a7-4f04-bfcc-cb7cea8b5bb7/gpmc.msi

http://download.microsoft.com/download/a/d/b/adb5177d-01a7-4f04-bfcc-cb7cea8b5bb7/gpmc.msi

Figure 3

4. Assign a name to your new Group Policy Object (GPO) and click OK.

Figure 4

5. Double-click on the name of your new GPO.

Figure 5

6. Click OK on next dialog box.

Figure 6

7. Right-click on your new GPO and select Edit.

Figure 7

8. Expand the Software Settings folder found in Computer Configuration, then right-click Software Installation and choose New > Package.

Figure 8

9. Browse to the location of your MSI package, select it, and click Open.

Figure 9

10. Remember that MSI packages can be created with tools such as Install Shield. MSI compressed files are the default choice for the MS Windows Server 2003 policy usage method. Select Assigned for deployment method, and then click

OK.

Figure 10

11. Upon next logon for users/and or computers, within the organizational unit (OU) specified above, the application will appear in the start menu. To install, simply launch the application from its icon located within the start menu.

Figure 11

As you can see, once you’ve done some initial homework and you have your MSI image, it doesn’t really matter if you have 10 or a 1,000 users in your group. As long as they’re in the group, you can apply the policy and they will get the image you created. The best part is that this happens at the OS level, which means everyone will get it.

More Tips for Updates

Here are some additional tips to keep in mind when doing updates:

● Automate as much as you can to simplify your management work. Make sure you have access to all the systems and tools you’re going to work with. (You’d be amazed at how much not having the appropriate admin rights affects a process.) Check with the people handling your facilities. You don’t want to start an

automatic update when they’ve scheduled a “lights out” in your buildings.

● Follow a strict Q/A process to filter any defective releases or builds. Once a “qualified” application has been selected, you can use an appropriate and efficient delivery method.

● Consider how users are going to be affected. Updating tools is not just a technical task. What might look wonderful to you might be a nightmare for users. Keep in mind that clear communications and constant attention to customer feedback help to ensure eventless deployments.

● Test and verify the method you’re going to use. Don’t wait until the last minute to find out the scripts were wrongly configured or something doesn’t work. It’s very healthy to have redundant delivery methods and a proven “back out” strategy. In fact, you should always have a way to back things up the way there were before, just in case. This preparation allows for a more stable process and will give you some peace of mind.

Large applications can be effectively distributed simultaneously to multiple sites and hundreds of users in a short period of time, using custom scripts and customized applications. For example, we have been able to deploy a full Pro/ENGINEER package to almost 500 workstations in less than 15 minutes! Explore and experiment with different options. There’s no magic bullet. Find what fits you best and get the most out of it.

Israel Pabón is a senior mechanical and applications engineer for Raytheon in Sudbury, MA. He can be reached by email at [email protected].



Going Native—Finding Qualified Pro/ENGINEER PartnersBy Greg Saisselin, ProeSuppliers.com

Everyone understands the benefits of associativity and the value of maintaining a single native file format through the entire product development process. That’s why thousands of companies made significant investments in Pro/ENGINEER over the past decade. However, many suppliers may or may not use different CAD systems such as CATIA®, Unigraphics® and others too numerous to mention. So when outsourcing product development services, should a Pro/ENGINEER-based organization sacrifice their investment and the valued benefits of Pro/ENGINEER ?

Baby STEPs

Despite the best intentions and efforts of talented software engineers, the goal of seamless data exchange between heterogeneous CAD systems remains elusive. Nearly a quarter century has passed since the inception of a vendor-neutral means for transferring design geometry, the Initial Graphics Exchange Specification (IGES).

Yet IGES, along with its successor STEP (ISO 10303), have failed to produce a stable environment for sharing design information within product development teams.A survey conducted by Tenlinks.com and Proficiency, Inc. revealed no companies

The answer is they don't have to. ProeSuppliers.com solves the daunting challenge of identifying qualified resources that can help your company maintain and extend the benefits of owning Pro/ENGINEER. Our focus is in the networking of companies so they can benefit from a seamless environment from concept to production.

How It Works

ProeSuppliers.com acts as a centralized database for outsourcing companies to identify industry-distinct resources with Pro/E capabilities. Our proprietary application lets you search by such variables as industry expertise, service description, geographic location, and key words that relate to any possible service, material, capability, and so forth.

Proesuppliers.com delivers results in a "best match" format based upon the selected search criteria. These criteria can be as specific or as broad as you want. The search system also takes into consideration that most suppliers offer various services that are not covered under one descriptive name, and often cater to multiple industries. We call this "sequential search capabilities," identifying every possible supplier that can satisfy the required service based upon the selected criteria.


Managing Change












http://www.caddigest.com/subjects/cad_translation/select/041604_interoperability_survey.htm



http://www.proesuppliers.com/

among the respondents accepted product designs from their suppliers in either of these exchange protocols. Two-thirds instead required 2D electronic drawings and nearly half also demanded 3D models in their native CAD formats. Thus, while IGES and STEP may be useful for some applications, they do not solve the issue of interoperability for supplier interactions.

At ProeSuppliers.com, you can use the search capabilities to locate the service provider that you need.

Benefits to Suppliers and Industry Partners

Each search performed in ProeSuppliers.com generates data that drives detailed graphical results in the suppliers’ member page. From this information, companies can tailor their listings to meet and communicate currently valued services and requirements. And this real-time communication can happen on even the most modest of marketing budgets. With an annual listing fee of $595.00, any supplier—not just the “rich and famous”—can benefit from this service.

Seeing the huge potential benefits for members and partners alike, PTC/USER is forming a strategic alliance with ProeSuppliers.com. According to Kevin Johnson, Executive Director for PTC/USER and head of new business development efforts, “the launch of the partnership with ProeSuppliers.com leverages the unique capabilities of each organization. Both are leaders in their respective areas and together, we will make available a dynamic and desperately-needed resource that surpasses those offered by any other user network in the world.”

Under its strategic alliance agreement, ProeSuppliers.com will provide Industry Partners new, effective ways to connect directly with the user community. For example, partners can take advantage of such benefits as resource identification services, supplier listing services, marketing and advertising programs, national and international employment opportunities, supply chain management services, and PTC software packages.

If you are in need of Pro/ENGINEER-related services, please check out ProeSuppliers.com today. You'll be glad you did!

Greg Saisselin is president of ProeSuppliers.com in Avon, Connecticut. He can be reached via e-mail at [email protected].




Changing the Order of “Save a Copy” File Typesby Greg Kemner, Northrop Grumman–Cutting Edge Optronics

The config option preferred_save_as_type lets you change the order of the options in the “save a copy” dialog box dropdown menu. This means your most frequently used “save as” file types will appear at the top of the list, eliminating the need to scan through the list every time.

For example, just add these settings to your config file:

Preferred_save_as_type STEP

Preferred_save_as_type JPEG

The “save a copy” dropdown menu will display the STEP file type and then the JPEG file type as the first two items in your list, in whatever order you entered them into your config file.


Managing Change












Figure 1. Default order of the “save a copy” dialog box dropdown menu.

Figure 2. The same list after adding the options to the config.pro file. Note the file types

that are now the first two items in the list.

Greg Kemner is a mechanical engineer / CAD systems administrator at Northrop Grumman–Cutting Edge Optronics in St. Charles, Missouri, USA. He can be reached by email at [email protected].


Another Take on Decalsby Jason Baggett, Rheem Manufacturing Co. A/C Division

Following up on John Randazzo’s tips for using decals (Fall 2004 issue), this article

describes another approach to enhancing the realism of your Pro/ENGINEER® models. By structuring Pro/E’s hidden capability to create labels, you can incorporate a representation of an actual finished product in your parts and assemblies. In addition to being flexible, intuitive, and natural, this technique also overcomes several problems related to the application of decals to an end product.

Here are a few things you need to do before you get started.

Setting Pro/ENGINEER Operating Parameters

In order for Pro/ENGINEER to understand what you are doing, you need to define the system option config.pro. You should set this up right away so that you have no problems locating the information source once you begin the procedure. This option is the hidden key to success.

In Wildfire™ 1.0, access the config.pro settings under the pull-down menu Tools, Options. The setting to add is the highlighted text in Figure 1.

Figure 1

The option texture_search_path allows you to assign a directory to access images for label application. This option maps the storage location drive that will be needed on all subsequent operations. The Value in the Options window will be the location where the images are stored. I suggest that this location should be a secure environment that’s not easily accessed by unauthorized users. By adding this option, you’re not only giving


Managing Change












http://www.profilesmagazine.com/p29/tips_randazzo.html

intelligence to the part with graphics, but also enabling Pro/ENGINEER to recognize target artwork.

Creating the Label Graphics

Before continuing, you need to decide how you want to create the artwork. The two methods I’ve found that work are to use a quality graphics program or to scan an existing graphic. Whichever approach you take, the end result should be a graphic file with a TIF extension. While more labor-intensive, the graphics program may give a better image. Scanning is faster but it creates a larger file size and more distortion when the image is closely examined.

I use Adobe Illustrator® to create my graphics. This program lets you create multi-colored images and text that can also be used for your label vendor. It also enables you to efficiently manage the artwork in a controlled environment. Saving the finished piece as a .tif file allows close zoom ratios without distortion while maintaining small file sizes. You can also edit the files using Illustrator, which you cannot do with the scanned image.

Label Name

When your artwork is done and you’re ready to save it, there is one major consideration. The file name of both the artwork and the Pro/ENGINEER part have to be the same. This is mandatory when the label is mapped to the Pro/E part. This process looks for similarity by naming convention. If it’s not an exact match, Pro/ENGINEER will not remember the location or file and you will have to reapply the image each time you open. This takes care of the intuitive aspect of this procedure. Because of the name commonality, Pro/ENGINEER creates a relationship so that once this part is mated with the image, it will appear everywhere that part is found.

Label Sizing and Geometry

Both artwork and Pro/ENGINEER data can be made to the exact size that they are to appear. By doing this, you are creating realism for your product with actual geometry. The label can be easily maneuvered to cover the surface of the part. When you place the image, you can do it on a flat surface or any nonplanar surface. While the mechanics of placing / sizing a graphic may vary, the final product should be the same.

Once you have a label file and have set the Pro/ENGINEER parameters, create a part file that has the exact dimensions as your label. You need not be concerned about label geometry. The label can be placed on the part file no matter whether it’s a circle, square or other shape. All you have to do is maneuver the image to fit properly in the Colors and Appearance area.

Procedure

Applying the label is relatively simple. Before proceeding, investigate the procedure and become acquainted with all the functions and instructions. This will allow you to apply correct placement settings for the graphics.

It is easiest to have the solid part oriented to the front. This places the surface that will have the label facing you. In Pro/ENGINEER:

1. Create a new solid part named the same as the label (Figure 2).

2. Part thickness needs to reflect actual material thickness of the label.

3. From the View pulldown menu, select the Color and Appearances option. This opens the Appearance Editor.

4. Add a new color to the Appearance Editor.

Figure 2

5. Under the Map tab on the Appearance Editor (Figure 3), check the (white) toggle box opposite “Decal” and then click in the preview box just to the left of the toggle box. This maps the label graphics file and opens the Appearance Placement dialog box (Figure 4).

Figure 3

Figure 4

6. Add the label texture by clicking the “+” on the Appearance Placement dialog box (top right).

7. This opens a file selection dialog box. Navigate to where the graphic images are stored, select the desired image, and click the open button

8. The .tif file is now attached and ready to be placed on the part surface.

9. Highlight the graphic image and then, from the Appearance Placement dialog box, start applying constraints to label positioning.

A. Set the Mapping constraint to Planar for a one-sided application.

B. Set the Copies constraint Single.

10. Close the Appearance Placement dialog box, which returns you to the Appearance Editor (Figure 5).

11. Under Assignment, select Surface from the pulldown menu.

12. Select the surface to which the graphic should be applied. Accept this surface by pressing the middle mouse button. With your desired surface assigned, click Apply.

Figure 5

13. The label may come in perfectly the first time. Typically it will come into the surface where you have to maneuver it or adjust the sizing and placement. Don’t worry if you don’t see it— it’s there and just needs to be reoriented.

Figure 6

14. Notice that the image has appeared to the right of the Decal area of the Appearance Placement dialog box. This confirms the decal is mapped.

15. To adjust sizing and placement, click the preview box displaying your image. The Appearance Placement dialog box allows you to apply the correct placement settings for the graphics. Scale and Position may need the most work. Scale does exactly what it says: X scales left to right, and Y scales top to bottom. Position works the same way, moving the image up and down or left to right. The Rotate option may come in handy at some point during your practice or work.

16. Once you are satisfied with the placement and sizing, simply close all dialog boxes and Save the part.

When the finished label is used in assemblies, it adds to the realism of the finished product (Figure 7). Note that this procedure lets you place the part in assemblies but not in drawings. I understand that a future release of Wildfire will address this issue.

Figure 7

Visualization

ProductView® 7.0 has the capability of publishing textures by using the above method. By publishing the labels in ProductView, you will be able to mimic the actual end product. To publish the labeled parts, however, you will need an updated Object Adapter with the texture option.

1. Initial ProductView 7.0 setup depends on your individual situation. To publish the labeled parts and assemblies, you need to specify a setting in the rcpedit dialog box. Navigate to PTC/productview_adapters7.0\bin on your hard drive and drag the proe2pv.rcp onto rcpedit.exe.

2. This opens the rcpedit dialog box. Under Advanced at the top, go to the Miscellaneous tab. At the bottom left you will see Convert. Check the box beside Textures and Save (Figure 8). Specific to your installation, you may have to alter other rcpedit options to acquire the end result of the published textures.

Figure 8

3. Now that the settings are established, you can publish Pro/E parts and assemblies that have textures. The task is no different than before, with exception of the new rcpedit option. Once the part and/or assembly have been published, you now have a realistic model of the actual product (Figure 9). This helps in visualizing end products with appropriate colors and placement.

Figure 9

By using this method and the part and texture naming convention, you also enable an exact Bill of Materials within both ProductView and Pro/ENGINEER.

Jason Baggett is a senior draftsman at Rheem Manufacturing Co. A/C Division in Fort Smith, Arkansas, USA. He can be reached by email at [email protected].


How to Update the Drawing System Parameter &todays_date Before Printingby Ceferino Sanchez of ASTEC Power, a Division of Emerson Network Power

The drawing system parameter &todays_date becomes a nonparametric note after placement as either a note or a table cell entity in a drawing form. Suggestions from the Pro/ENGINEER forums include placing the drawing form with the parameter &todays_date just before printing, but this is not always practical if revisions follow. This tip provides a method for semi-automating &todays_date in Pro/ENGINEER Wildfire 2.0 to reflect the date of the host computer prior to printing.

1. Select Format, Symbol Gallery, Define to create a symbol named DATESTAMP, with only the variable text set to the preset value of &todays_date.

2. Select Insert, Note, Make Note.


Managing Change












3. Type in “date” with backslashes so the symbol recognizes it as a variable text. (Text Style in this example is isofont.)

4. Define the symbol attributes.

5. Define Allowed Placement Type.

6. Define the Preset Values for the variable text as &todays_date.

7. Store the symbol DATESTAMP in your symbol directory.

8. Select Insert, Drawing, Symbol, Custom to insert the symbol into the drawing. Alternatively, you can create start drawing templates with this symbol already placed and added in a layer named DATESTAMP. This lets you blank out the date when it is not required for printing. In the example below, the config option todays_date_note_format is set to %dd-%MMM-%yyyy.

9. Place the symbol.

10. In the newly created layer DATESTAMP, include the symbol DATESTAMP.

11. Verify that the layer DATESTAMP contains the symbol DATESTAMP.

12. Create a mapkey to be saved in the config.pro that updates the variable text in the symbol. The trick here is to find the symbol in the drawing, edit its properties, and click OK without doing anything else in the Symbol Properties dialog box. Doing so updates the variable text to the date of the host computer. Make sure you only have one DATESTAMP symbol in your drawing or the mapkey will not work. Select Tools, Mapkeys, New and then create the mapkey ‘ud’.

13. Start recording with CTRL+F and enter parameters as shown below.

14. Continue with Find Now, then move the found symbol to the selected column, and close the Search Tool box.

15. Continue with Edit, Properties.

16. Click OK on the Custom Drawing Symbol dialog box.

Below is the mapkey as recorded in config.pro:

mapkey ud @MAPKEY_LABELUpdate Datestamp;\

mapkey(continued) ~ Activate `main_dlg_cur` `ProCmdMdlTreeSearch.edit_t`;\

mapkey(continued) ~ Open `selspecdlg0` `SelOptionRadio`;~ Close `selspecdlg0` `SelOptionRadio`;\

mapkey(continued) ~ Select `selspecdlg0` `SelOptionRadio`1 `Drawing Symbol`;\

mapkey(continued) ~ Open `selspecdlg0` ÈxtRulesLayout.ExtBasicNameLayout.BasicNameList`;\

mapkey(continued) ~ Close `selspecdlg0` ÈxtRulesLayout.ExtBasicNameLayout.BasicNameList`;\

mapkey(continued) ~ Select `selspecdlg0` ÈxtRulesLayout.ExtBasicNameLayout.BasicNameList`1 \

mapkey(continued) `DATESTAMP`;~ Activate `selspecdlg0` ÈvaluateBtn`;\

mapkey(continued) ~ Activate `selspecdlg0` ÀpplyBtn`;~ Activate `selspecdlg0` `CancelButton`;\

mapkey(continued) ~ Select `main_dlg_cur` `MenuBar1`1 Èdit`;\

mapkey(continued) ~ Close `main_dlg_cur` `MenuBar1`;\

mapkey(continued) ~ Activate `main_dlg_cur` Èdit.psh_dwg_props`;\

mapkey(continued) ~ Activate `drawing_sym_asynch` ÒK_modif_push`;

17. You can prefix this mapkey to your printing mapkey so that your drawing will have this persistent datestamp. In this case, I appended the ‘ud’ mapkey before the Plot to PDF mapkey.

The example below is the single-sheet PDF print mapkey. The batch file, plotpdf.bat, renames the plt file to a ps file, then calls the postcript file and runs the PDF program (e.g., Adobe Distiller). The following is just one of several ways to implement the printing mapkey, which will depend on your company standards. If you hide the layer DATESTAMP, the ‘ud’ mapkey will still update the variable text but the symbol will not print.

18. With a drawing in the active window with the symbol DATESTAMP, go to Tools,

Mapkeys, New and create the mapkey @plotpdf. Highlight the graphics window and type ‘ud’ to activate the Update Datestamp mapkey.

19. Start with CTRL+P and then choose the parameters shown above.

20. Continue with this menu tab and choose parameters as shown.

21. Continue by clicking OK on all windows and then enter the operating system script.

22. Below is the Print to PDF mapkey prefixed by the ‘ud’ mapkey.

mapkey @plotpdf @MAPKEY_NAMEPlot a single sheet drawing file as PDF full \

mapkey(continued) scale;@MAPKEY_LABELPlot Single Sheet PD&F;%ud;\

mapkey(continued) ~ Select `main_dlg_cur` `MenuBar1`1 `File`;~ Close `main_dlg_cur` `MenuBar1`;\

mapkey(continued) ~ Activate `main_dlg_cur` `File.psh_print`;~ Select `print` `CascadeButton1`;\

mapkey(continued) ~ Close `print` `CascadeButton1`;~ Activate `print` `Generic Postscript`;\

mapkey(continued) ~ Activate `print` `ToFile`1 ;~ Activate `print` `ToPrinter`0 ;\

mapkey(continued) ~ Activate `print` `Configure`;\

mapkey(continued) ~ Select `print_config` `r_opt_ctrl`1 `Model_sheet`;\

mapkey(continued) ~ Open `print_config` ò_plot`;~ Close `print_config` ò_plot`;\

mapkey(continued) ~ Select `print_config` ò_plot`1 `Full Plot`;\

mapkey(continued) ~ Update `print_config` ò_plot` `Full Plot`;~ Activate `print_config` ÒK`;\

mapkey(continued) ~ Activate `print` ÒK`;~ Activate `Print_file` ÒK`;

mapkey(continued) @SYSTEMstart w:\\\\pro_stds\\\\batch_files\\\\plotpdf.bat;

Ceferino Sanchez is lead engineer and Pro/E administrator at ASTEC Power, a division of Emerson Network Power in Quezon City, Philippines. He can be reached by email at [email protected].


Easy Axis Justificationby Steve Register, General Atomics Aeronautical Systems

In a view where crosshairs are displayed, clicking on one of the centerlines will move only that side of the line. With this technique, you can change all four leaders simultaneously.

1. Under normal crosshair expansion conditions, the leaders expand and compress one at a time as shown below.

2. Turning on the axis layer and clicking on the A_# allows the user to manipulate all of the leaders simultaneously.


Managing Change








More information about RUGs is available at our web site...





http://members.ptcuser.org/Resource.phx/rug/rug.htx

Steve Register is an engineer at General Atomics in San Diego, CA He can be reached via e-mail at [email protected].


Documents

Winter 2005