<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: Communicating revision changes to a vendor in 3D Part &amp; Assembly Design</title>
    <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55870#M40700</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would suggest this information be communicated to vendors the same way it's communicated to anyone not directly involved in making those changes. In other words, the anyone outside of the draftsman, designer, engineer, checker or project/dept manager. People such as the shop floor, assembly line, vendors, ERP/MRP entry, mfg. engineering, etc. need to know what changed every time a revision is made. The two most obvious solutions are to have those that made the changes (eng dept) list the changes OR to have each down-stream person do their own evaluation of what changed and hope they don't overlook something (let alone something critical).&lt;BR /&gt;&lt;BR /&gt; In Reply to Chris Rees:&lt;/P&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;I realize this is a little off topic, but how do you communicate revision changes to vendors? I know there is an analysis -&amp;gt; Compare drawings, but that doesn't provide a clear way to describe the change especially if you have moved a view.&lt;BR /&gt;&lt;BR /&gt;I know Acrobat Pro also compares PDFs but often it just highlights the whole page.&lt;BR /&gt;&lt;BR /&gt;Are people just handing the new drawings to the vendors and letting them work it out or is there other software out there to automate the process?&lt;BR /&gt;&lt;BR /&gt;Christopher Rees - Mechanical Engineer - ISR Systems&lt;BR /&gt;UTC AEROSPACE SYSTEMS&lt;BR /&gt;100 Wooster Heights Rd, Danbury, CT 06810 U.S.A.&lt;BR /&gt;Tel: +1 203 797 5490 Fax: +1 203 797 6637&lt;BR /&gt;christopher.rees@utas.utc.com&amp;lt;&lt;A href="mailto:christopher.rees@utas.utc.com'%3E" target="_BLANK"&gt;&lt;/A&gt; www.utcaerospacesystems.com&lt;A href="http://www.utcaerospacesystems.com"&gt;http://www.utcaerospacesystems.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;CONFIDENTIALITY WARNING: This message may contain proprietary and/or privileged information of UTC Aerospace Systems and its affiliated companies. If you are not the intended recipient please 1) do not disclose, copy, distribute or use this message or its contents, 2) advise the sender by return e-mail, and 3) delete all copies (including all attachments) from your computer. Your cooperation is greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 21 Apr 2014 14:58:56 GMT</pubDate>
    <dc:creator>DonSenchuk</dc:creator>
    <dc:date>2014-04-21T14:58:56Z</dc:date>
    <item>
      <title>Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55868#M40698</link>
      <description>I realize this is a little off topic, but how do you communicate revision changes to vendors? I know there is an analysis -&amp;gt; Compare drawings, but that doesn't provide a clear way to describe the change especially if you have moved a view.I know Acrobat Pro also compares PDFs</description>
      <pubDate>Sun, 13 Dec 2020 02:48:08 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55868#M40698</guid>
      <dc:creator>Chris3</dc:creator>
      <dc:date>2020-12-13T02:48:08Z</dc:date>
    </item>
    <item>
      <title>Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55869#M40699</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Christopher,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Well for starters that is why some companies add revision symbols (triangles, etc) on the drawing where a dimension, view or note was changed, added or deleted. This helps for internal or external use. In some cases an ECN will list every change, addition or deletion to a dimension, note or view in addition to an explanation and reason for the change. If possible that could be provided to the vendor.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In other cases when change documentation is not that detailed I have made highlighted mark-ups of prints in the past which could now be done with electronic editors. I have even made before and after snap-shots in put them in Word or Power Point and then added appropriate notations, arrows, highlights or descriptions as required to communicate the changes. I would do things like this when a vendor had quoted a preliminary drawing and it had not been formally released and thus not requiring ECN control and associated documentation.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All this might sound like a lot of work and it can be time consuming, but it is much better than getting a bad part later which can be very painful and costly and jeopardize a project or build or manufacturing. I presume there are electronic tools to help, but communications is the key.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sincerely,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mark A. Peterson&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Design Engineer&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Varel International&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:-" rel="nofollow noopener noreferrer" target="_blank"&gt;-&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;----------&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 23:29:44 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55869#M40699</guid>
      <dc:creator>mpeterson</dc:creator>
      <dc:date>2017-10-26T23:29:44Z</dc:date>
    </item>
    <item>
      <title>RE: Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55870#M40700</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would suggest this information be communicated to vendors the same way it's communicated to anyone not directly involved in making those changes. In other words, the anyone outside of the draftsman, designer, engineer, checker or project/dept manager. People such as the shop floor, assembly line, vendors, ERP/MRP entry, mfg. engineering, etc. need to know what changed every time a revision is made. The two most obvious solutions are to have those that made the changes (eng dept) list the changes OR to have each down-stream person do their own evaluation of what changed and hope they don't overlook something (let alone something critical).&lt;BR /&gt;&lt;BR /&gt; In Reply to Chris Rees:&lt;/P&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;I realize this is a little off topic, but how do you communicate revision changes to vendors? I know there is an analysis -&amp;gt; Compare drawings, but that doesn't provide a clear way to describe the change especially if you have moved a view.&lt;BR /&gt;&lt;BR /&gt;I know Acrobat Pro also compares PDFs but often it just highlights the whole page.&lt;BR /&gt;&lt;BR /&gt;Are people just handing the new drawings to the vendors and letting them work it out or is there other software out there to automate the process?&lt;BR /&gt;&lt;BR /&gt;Christopher Rees - Mechanical Engineer - ISR Systems&lt;BR /&gt;UTC AEROSPACE SYSTEMS&lt;BR /&gt;100 Wooster Heights Rd, Danbury, CT 06810 U.S.A.&lt;BR /&gt;Tel: +1 203 797 5490 Fax: +1 203 797 6637&lt;BR /&gt;christopher.rees@utas.utc.com&amp;lt;&lt;A href="mailto:christopher.rees@utas.utc.com'%3E" target="_BLANK"&gt;&lt;/A&gt; www.utcaerospacesystems.com&lt;A href="http://www.utcaerospacesystems.com"&gt;http://www.utcaerospacesystems.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;CONFIDENTIALITY WARNING: This message may contain proprietary and/or privileged information of UTC Aerospace Systems and its affiliated companies. If you are not the intended recipient please 1) do not disclose, copy, distribute or use this message or its contents, 2) advise the sender by return e-mail, and 3) delete all copies (including all attachments) from your computer. Your cooperation is greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2014 14:58:56 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55870#M40700</guid>
      <dc:creator>DonSenchuk</dc:creator>
      <dc:date>2014-04-21T14:58:56Z</dc:date>
    </item>
    <item>
      <title>Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55871#M40701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;One can easily do a detailed comparison of say Rev D vs. Rev C drawing using CreoView Drawing Overlay.  PTC doesn't make it all that easy but with some manual steps, one can provide the result to vendors in a relatively static way. Drawing Overlay is dependent on publishing to PLT rather than PDF format (one of the major decisions to make when setting up visualization).  If you give vendors access to say a Windchill Project and share Drawings to the Project, they can then utilize Drawing Overlay fully to explore differences interactively.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[cid:image001.png@01CF5D39.35D8E680]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Drawing Overlay within CreoView (and also older ProductView) is one of the relatively quiet "gems" in the system; surprising how few people seem to fully utilize.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Going back to Intralink 3.x days and continuing to now, we heavily use visualization (drawings are published to PLT, not PDF).  Use of Drawing Overlay is one of the primary reasons for using PLT in the face of many downsides.  We've fully integrated Drawing Overlay into our process; all checking is done using it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2014 15:10:54 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55871#M40701</guid>
      <dc:creator>MikeLockwood</dc:creator>
      <dc:date>2014-04-21T15:10:54Z</dc:date>
    </item>
    <item>
      <title>RE: Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55872#M40702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did Chris' actual question get anwered? I read it as "How to specify changes clearlyto a vendor" and what I think I read were how to compare revs within the PTC suite. Is that a valid assumption?&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Seems to me if the vendor has the ability to read native files then the suggestions are okay. But if they do not then there is an issue in my opinion.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;My .02 answering what I perceive as the actual question from Chris:&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;If the vendor does not have the ability to read native but can read 3D I suggest you send the latest version and the prior revin STEP, clearly named,exported from the same CSYS. Once imported the vendor can change the colors of the parts and easily see the changes from rev to rev.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;If the vendor can only read 2D then send dxf's of each rev exported from the same drawing origin. Same principle applies. By importing both dxf's over one another the changes are easy to see.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2014 23:44:59 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55872#M40702</guid>
      <dc:creator>DeanLong</dc:creator>
      <dc:date>2014-04-21T23:44:59Z</dc:date>
    </item>
    <item>
      <title>[External] Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55873#M40703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Actually my question was more software related. Internally we already have a process for communicating changes to vendors however it is a manual one (creating a from-to document using screen shots that is separate from the drawing). I was looking to see if other people had an automated way (software that generates a report) to communicate changes to vendors.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;All of the responses I have received so far implied that people are doing this manually as well with the exception of &lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 11:14:26 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55873#M40703</guid>
      <dc:creator>Chris3</dc:creator>
      <dc:date>2014-04-22T11:14:26Z</dc:date>
    </item>
    <item>
      <title>RE: [External] Communicating revision changes to a vendor</title>
      <link>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55874#M40704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've used Photoshop/ Photoshop elements as a go-to means of identifying changes between revisions. Much better than any other compare because it can be used to handle shifting views, changed view scales, views moved to other sheets, scanned drawings with skewed views against vector drawings.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;WIth a small amount of practice it eats up almost 2 minutes a sheet of any size, if one is dogging it and there's a lot of changes of the type mentioned above. Maybe more if it's a scan of a faxed copy made after a good sneeze on the glass of a print that got coffee spilled on it and rode in a back-pocket before being accidently crumpled and dumped in the trash. Those take longer, but see what ProductView does with the same input.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;The result is stored in a PDF such that all versions can pretty readily be stored over the life of a typical drawing.Very handy for finding and stopping those "When did that change!" moments.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;That said, there should be a separate document that spells out why the changes are being made to the design and what changes should be made to the drawing to accomplish those changes. This should be agreed on before the drawing is updated so the supplier doesn't need help to find what changed.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;The comparison makes certain that what was supposed to change did and what wasn't didn't, even if a lot of things got moved but they made no difference. After using the Photoshop technique a while you'll grow to really dislike drafters who nudge everything, just to pretty it up. Nudging is also something other software doesn't handle.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;I know I've posted the steps before, but it's late and I don't know if you care to know them.&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;x&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Apr 2014 04:49:27 GMT</pubDate>
      <guid>https://community.ptc.com/t5/3D-Part-Assembly-Design/Communicating-revision-changes-to-a-vendor/m-p/55874#M40704</guid>
      <dc:creator>kimndave9</dc:creator>
      <dc:date>2014-04-23T04:49:27Z</dc:date>
    </item>
  </channel>
</rss>

