<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PLM Exchange &#187; contentManager</title>
	<atom:link href="http://plmexchange.net/author/contentmanager/feed/" rel="self" type="application/rss+xml" />
	<link>http://plmexchange.net</link>
	<description>NX, Teamcenter, and the PLM Market</description>
	<lastBuildDate>Fri, 30 Jul 2010 13:22:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Wiki Style</title>
		<link>http://plmexchange.net/wiki-style/</link>
		<comments>http://plmexchange.net/wiki-style/#comments</comments>
		<pubDate>Sun, 25 Feb 2007 12:56:10 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=491</guid>
		<description><![CDATA[A PLM web site should be open for collaboration. Since a blog style site isn&#8217;t the best suited for this I have decided to create a wiki. A wiki will allow anyone to edit and create content. I&#8217;m in the begining stages of this new wiki style site and will post when it is open [...]]]></description>
			<content:encoded><![CDATA[<p>A PLM web site should be open for collaboration. Since a blog style site isn&#8217;t the best suited for this I have decided to create a wiki. A wiki will allow anyone to edit and create content. I&#8217;m in the begining stages of this new wiki style site and will post when it is open to the public. This site will still exist as a blog entry but the bulk of the effort will be focused on the Wiki. </p>
<p>News coming soon. If your interested in joining the Wiki as a early adopter and want to be involved early let me know in the comments or by the contact page and I&#8217;ll send out the URL.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/wiki-style/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Knowledge Fusion optional variable arguments</title>
		<link>http://plmexchange.net/knowledge-fusion-optional-variable-arguments/</link>
		<comments>http://plmexchange.net/knowledge-fusion-optional-variable-arguments/#comments</comments>
		<pubDate>Wed, 17 Jan 2007 03:06:27 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[Automation]]></category>
		<category><![CDATA[NX]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=490</guid>
		<description><![CDATA[An optional argument ia defined by parenthesis (), and one or many optional arguments are defined with &#8230; (three dots). Example would be to have optional many arguments: Defun: Average (Number &#8230; $nums) This example if a function called &#8220;Average&#8221; with optional arguments of type &#8220;Number&#8221; that can be one or many stored in a [...]]]></description>
			<content:encoded><![CDATA[<p>An optional argument ia defined by parenthesis <strong>()</strong>, and one or many<br />
optional arguments are defined with <strong>&#8230;</strong> (three dots).</p>
<p>Example would be to have optional many arguments:</p>
<p>        <strong>Defun: Average (Number &#8230; $nums)</strong></p>
<p>This example if a function called &#8220;<em>Average</em>&#8221; with optional arguments of<br />
type &#8220;<em>Number</em>&#8221; that can be one or many stored in a list called &#8220;<em>$num</em>s&#8221;.</p>
<p>One way to access the $nums is by creating an expression block:</p>
<p>@{<br />
     $total << loop {<br />
     for $num in $nums;<br />
     sum $num;<br />
  };</p>
<p>So in Knowledge Fusion it is possible to have a function with optional arguments and it is possible to have a function to allow one or many arguments. The design patterns I try to stick to does not have a need for variable arguments but the optional feature is nice if you can have default values then override if necessary.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/knowledge-fusion-optional-variable-arguments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mass Properties</title>
		<link>http://plmexchange.net/mass-properties/</link>
		<comments>http://plmexchange.net/mass-properties/#comments</comments>
		<pubDate>Mon, 18 Dec 2006 20:51:30 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[NX]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=489</guid>
		<description><![CDATA[When you do a Mass Properties on an object (Analysis -> Mass Properties) you have an option to &#8220;Display Annotation&#8221;. Toggle this on and select a solid. This will present you with a annotation and the ability to drag the value attached by a leader around the screen. This will remain on the screen until [...]]]></description>
			<content:encoded><![CDATA[<p>When you do a Mass Properties on an object (Analysis -> Mass Properties) you have an option to &#8220;Display Annotation&#8221;. Toggle this on and select a solid. This will present you with a annotation and the ability to drag the value attached by a leader around the screen. This will remain on the screen until the screen is refreshed. An undo will also do an Refresh and the annotation will disappear.</p>
<p>There is also a save button that will create associative expression. In the expression dialog change the Listed Expressions to &#8220;Measurements&#8221;. You will have 5 expressions, Surface area, volume, mass, weight, radius of gyration.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/mass-properties/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Sketcher Best Practices</title>
		<link>http://plmexchange.net/sketcher-best-practices/</link>
		<comments>http://plmexchange.net/sketcher-best-practices/#comments</comments>
		<pubDate>Tue, 12 Dec 2006 18:15:22 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[NX]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=488</guid>
		<description><![CDATA[When you create a sketch, you should always use a Datum Axis as the horizontal and vertical references. The attachment plane should be a datum plane but it could be attached to a face if you don&#8217;t mind the dependency. Why would you use a Datum Axis for the horizontal and vertical reference? Datum Axis [...]]]></description>
			<content:encoded><![CDATA[<p>When you create a sketch, you should always use a Datum Axis as the horizontal and vertical references. The attachment plane should be a datum plane but it could be attached to a face if you don&#8217;t mind the dependency. Why would you use a Datum Axis for the horizontal and vertical reference? Datum Axis give you a direction. So when you reattach a sketch, copy paste into a new file, or in a UDF the dimensions will not flip unexpected on you. I have  been burned a few times because of this. I used to use Datum planes as the Horizontal and vertical, never again. A csys will accomplish the same thing as long as you pick the axis when associating the dimensions.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/sketcher-best-practices/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Teamcenter Slow? Want to know why?</title>
		<link>http://plmexchange.net/teamcenter-slow-want-to-know-why/</link>
		<comments>http://plmexchange.net/teamcenter-slow-want-to-know-why/#comments</comments>
		<pubDate>Fri, 10 Nov 2006 14:45:58 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[Teamcenter]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=437</guid>
		<description><![CDATA[If you are having performance issues with Teamcenter and you want to have some sort of clue as to what is going on, set the following variable: set IMAN_SLOW_SQL=1 When running Teamcenter and something takes longer then there will be some eplaination in the syslog of what is going on. It probably won&#8217;t be really [...]]]></description>
			<content:encoded><![CDATA[<p>If you are having performance issues with Teamcenter and you want to have some sort of clue as to what is going on, set the following variable:</p>
<p>set IMAN_SLOW_SQL=1</p>
<p>When running Teamcenter and something takes longer then <your value in seconds> there will be some eplaination in the syslog of what is going on. It probably won&#8217;t be really clear what to do but it will explain the area and what it is trying to do in some cryptic way. In this case i set <strong>IMAN_SLOW_SQL=1</strong>, 1 being seconds, this may register a lot of issues depending on your environment, set it to 2 seconds to filter out the syslog and narrow down the major performance issue.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/teamcenter-slow-want-to-know-why/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>NX Part Name Versions</title>
		<link>http://plmexchange.net/nx-part-name-versions/</link>
		<comments>http://plmexchange.net/nx-part-name-versions/#comments</comments>
		<pubDate>Tue, 17 Oct 2006 20:15:52 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[NX]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=382</guid>
		<description><![CDATA[NX has this mechanism for loading the latest version of a component in Native mode (Non Teamcenter Environment). In the File -> Options -> Load Options There is an option &#8220;Load Latest&#8220;. By default it is greyed out. To enable this you must set the Customer Defaults file. File -> Utilities -> Customer Defaults -> [...]]]></description>
			<content:encoded><![CDATA[<p>NX has this mechanism for loading the latest version of a component in Native mode (Non Teamcenter Environment). In the <strong>File -> Options -> Load Options</strong> There is an option &#8220;<strong>Load Latest</strong>&#8220;. By default it is greyed out. To enable this you must set the Customer Defaults file.</p>
<p>File -> Utilities -> Customer Defaults -> Assemblies (section) -> Site Standards (sub section) -> Part Name Versions (tab). There you will see five sections. </p>
<p><imageStyle><a href="http://www.plmexchange.net/wp-content/uploads/2006/10/partNameVersion.PNG" rel="lightbox" title="Part Name Version"><img id="image405" src="http://www.plmexchange.net/wp-content/uploads/2006/10/partNameVersion.thumbnail.PNG" alt="Part Name Versions" /></a></imageStyle></p>
<p>I would suggest this type of version control go into the Site defaults file, but I&#8217;m showing the user defaults file just because I had this set when I was doing my testing. Now the syntax is pure Regular Expressions with no short cuts. This is a simple one, that expects a number 0 -> 9 and it has to be 8 digits long, seperated by a &#8216;.&#8217; (dot) then a number 0 -> 9 that has to be 3 digits long. The part name match is just the ending four characters. Should have put the dot in its own group but this was just a test, to get it working this needs to be seperated.  Then the last setting is the type of version. So NX knows what is the oldest or newest. This would be set to numeric for this example. Another fix I need to do for this to work. Again this is just a test. </p>
<p>Now that this is set. Apply the customer defaults, close and reopen NX. Now in the load options the &#8220;load latest&#8221; option is available. Also &#8220;<strong>Allow Substitution</strong>&#8221; should be enabled, otherwise this is all useless. And the Load Method should <strong>Not</strong> be &#8220;As Saved&#8221; but instead one of the other optons. </p>
<p>Now you can have a part file 12345678.001 &#038; 12345678.002. When you open the assembly that has this component added it will use the latest version. </p>
<p>Pretty cool for those not using Teamcenter.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/nx-part-name-versions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating Bitmaps for NX3+</title>
		<link>http://plmexchange.net/creating-bitmaps-for-nx3/</link>
		<comments>http://plmexchange.net/creating-bitmaps-for-nx3/#comments</comments>
		<pubDate>Thu, 12 Oct 2006 22:00:04 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[NX]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=368</guid>
		<description><![CDATA[Over the years there have been a few formats for bitmaps in NX. Since toolbars started to appear then icons in the menus, and bitmaps in the dialogs the formats have changed. Originally it was bmp format of the size 24 and 32 for color and monochrom with 16 colors. Along with the different format [...]]]></description>
			<content:encoded><![CDATA[<p>Over the years there have been a few formats for bitmaps in NX. Since toolbars started to appear then icons in the menus, and bitmaps in the dialogs the formats have changed. Originally it was bmp format of the size 24 and 32 for color and monochrom with 16 colors. Along with the different format also was a naming convention of image_lc.bmp image_sc.bmp, image_sm.bmp, image_lm.bmp. For large color, small color, large monochrome, and small monochrome. With NX3 and newer NX now can scale the drawings down or up to fit the size of the interface the user picks. Scaling up never looks good so my experience is to create one color image using 24bit resolution at a size of 48&#215;48. Name it image.bmp (replacing it with your name). Notice there are not any additional naming convention on the end. So instead of having two images to maintain,  you know have one. Any area that is meant to be transparent should be magenta (R=192, G=192, B=192). NX will use an alpha mask to convert that to transparent. When the user changes their O/S Background image the icon will still look good. If want partially transparent you will need to create two images, one black background and the other white background naming the images. image.21.white.bmp and image.21.black.bmp acordingly. </p>
<p>Personally i would never do partially transparent just because of the additional maintence. This format only works for menus and toolbar icons. The styler images still do not use this alpha mask and size standard yet. Perhaps NX5 everything will be the same image. </p>
<p>Where do you put these images for your custom menus and toolbars? One option is to put it in the application folder, or put it in the bitmap folder defined by the custom bitmap, or use set the custom directory environment variable but append each directory where a folder is located at using the custom bitmap environment variable=environment variable; new path.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/creating-bitmaps-for-nx3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Free 2D Design Tool (Solid Edge 2D)</title>
		<link>http://plmexchange.net/free-2d-design-tool-solid-edge-2d/</link>
		<comments>http://plmexchange.net/free-2d-design-tool-solid-edge-2d/#comments</comments>
		<pubDate>Thu, 12 Oct 2006 15:14:25 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[Solid Edge]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=367</guid>
		<description><![CDATA[UGS is offering a free 2D drafting tool. This free tool offers a way to to transition from 2D AutoCAD (which has a recuring cost) to the free SolidEdge 2D drafting tool. This not only saves companies from the cost of AutoCAD but also opens up the available products in Solid Edge. When the company [...]]]></description>
			<content:encoded><![CDATA[<div class="imageStyle"><a href="http://www.solidedge.com/free2d/images/Free2D.jpg" rel="lightbox" title="Solid Edge Free 2D Drafting"><img src="http://www.solidedge.com/free2d/images/Free2D.jpg" alt="Solid Edge Free 2D Drafting" /></a></div>
<p>UGS is offering a free 2D drafting tool. This free tool offers a way to to transition from 2D AutoCAD (which has a recuring cost) to the free SolidEdge 2D drafting tool. This not only saves companies from the cost of AutoCAD but also opens up the available products in Solid Edge. When the company is ready you can upgrade from SolidEdge 2D to 3D. It has the same interface with additional capabilities to make the transistion to 3D. If you out grow SolidEdge 3D you can upgrade to NX. NX and Solid edge can read each others file types, so there is no need to translate data. Preserve your investment in user training in the interface when you upgrade to SolidEdge 3D. It is truly a remarkable approach they are doing. I just wish you could download the software without providing all the information. There should be a mechanism in the product to request upgrade, then get the companies information.</p>
<p><strong>From UGS&#8217;s web site</strong></p>
<blockquote><p>Solid Edge 2D drafting demonstrates UGSâ€™ commitment to helping companies control costs. Whether you are using 2D company-wide or for specific 2D design processes, you will benefit from Solid Edge 2D Drafting. Solid Edge 2D Drafting capitalizes on 10 years of production-proven capabilities developed for Solid Edge, and offers excellent drawing layout, diagramming, annotation and dimensioning controls that automatically comply with a wide range of drafting standards â€“ including ISO, ANSI, BSI, DIN, JIS and UNI. And it is absolutely FREE to download and use.<br />
Solid Edge 2D Drafting includes a wealth of tools designed to ease the transition of 2D AutoCAD users updating to Solid Edge, including import wizards, WYSIWYG of imported files (matching of AutoCAD fonts and color schemes) and many other capabilities that make it a compelling application for AutoCAD 2D users looking for more value and productivity from their 2D CAD seats.</p></blockquote>
<p>Go to <a href="http://www.solidedge.com/free2d/default.htm">Solid Edge Free 2D Drafting</a> for more information.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/free-2d-design-tool-solid-edge-2d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UGS NX Calendar 2007</title>
		<link>http://plmexchange.net/ugs-nx-calendar-2007/</link>
		<comments>http://plmexchange.net/ugs-nx-calendar-2007/#comments</comments>
		<pubDate>Mon, 02 Oct 2006 13:00:09 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[NX]]></category>
		<category><![CDATA[UGS NEWS]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=338</guid>
		<description><![CDATA[Found a link to the UGS Calendar 2007 submission page. Get some exposure for your company and submit an image.]]></description>
			<content:encoded><![CDATA[<p><imageStyle><img src="https://www.ugs.com/promotions/calendar2006/images/2006/cameron.jpg" alt="UGS Calendar" /></imageStyle><br />
Found a link to the <a href="www.ugs.com/calendar2007">UGS Calendar 2007</a> submission page. Get some exposure for your company and submit an image. </p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/ugs-nx-calendar-2007/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Convert Spline to lines and Arcs</title>
		<link>http://plmexchange.net/convert-spline-to-lines-and-arcs/</link>
		<comments>http://plmexchange.net/convert-spline-to-lines-and-arcs/#comments</comments>
		<pubDate>Mon, 18 Sep 2006 18:02:28 +0000</pubDate>
		<dc:creator>contentManager</dc:creator>
				<category><![CDATA[NX]]></category>

		<guid isPermaLink="false">http://www.tolsnet.com/plmexchange/?p=306</guid>
		<description><![CDATA[If you have a spline and want to convert it to arcs and lines, us this option: Insert -> Curve from Curves -> Simplify UPDATE Starting with a Spline I used the studio spline available under &#8220;Insert -> Curve -> Studio Spline&#8221;. Picked four points and ok on the dialog. Now we have one spline. [...]]]></description>
			<content:encoded><![CDATA[<p>If you have a spline and want to convert it to arcs and lines, us this option:<br />
<strong><br />
Insert -> Curve from Curves -> Simplify</strong></p>
<p><strong>UPDATE</strong><br />
Starting with a Spline<br />
<imageStyle><a href="http://www.plmexchange.net/wp-content/uploads/2006/10/studioSpline.PNG" title="Studio Spline" rel="lightbox"><img id="image393" src="http://www.plmexchange.net/wp-content/uploads/2006/10/studioSpline.thumbnail.PNG" alt="Studio Spline" /></a></imageStyle></p>
<p>I used the studio spline available under &#8220;Insert -> Curve -> Studio Spline&#8221;. Picked four points and ok on the dialog.</p>
<p>Now we have one spline. To break it up into arcs and lines, use the &#8220;Insert -> Curve from Curves -> Simplify&#8221; option. Pick the option you want to have happen. In this case I&#8217;m selecting delete the original curve and only leave me the new simplified spline. Select the spline and ok. What you are left with is a line that is made up of lines and arcs depending on what is the simplest geometry to get the same curve.</p>
]]></content:encoded>
			<wfw:commentRss>http://plmexchange.net/convert-spline-to-lines-and-arcs/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
