Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to Learn more.

Process Plan: Operation: Part Allocation: Display Reference Designators whether Usage or Occurrence

Process Plan: Operation: Part Allocation: Display Reference Designators whether Usage or Occurrence

We( Contract Electronic Board Manufacturer) would like PTC to reconsider that Showing Reference Designator in Part Allocation/Work Instructions should be standard functionality. 


Column was Visible in 11.X Part Allocation Table but did not Work.  PTC has resolved with SPR by removing the Column in 12.0.


************Current Ability*******

Current Process 11.0:


  1. Part Allocation: Usage to an Operation
  2. User can see Usage Attribute: Line Number in Part Allocation Tab then must Select Related to get to Related Assembly to go Uses Tab to Sort by Usage Attribute Line Number to then see Usage Attribute Reference Designator.

OCCURRENCE: 11.1 Part Tree Picker (or 11.0 Creo View)

  1. Part Allocation in Related Part Tree Picker to Occurrence Mode, Additional Column Ref Des to Show Ref Des of each Occurrence.  Allocate a Specific Occurrence to Operation
  2. User can See QTY but has No Idea Which Occurrence is allocated (Unless with CAD as you can see in Visualization) as no Ref Designator Displayed in Part Allocation.
    1. No Way for User to determine which occurrence goes on the electrical board – Assembly Document must be created to answer that Question. 
    2. User can go through Related/Related Assembly to See How Much QTY is a Subset of Total QTY.
    3. Work-Around – User Allocated Occurrence must manually type to Description Field

***** Current Usage*****

We have a Custom ERP/XML Output which does output Operation, Allocated Parts and then Shows the Reference Designators (Since it is there - You can see Occurrence Path in Creo View Metadata) Spefically Allocated to the Operation.    So we can import the Information into our Oracle MRP.


We can add Reference Designator to Tree Picker Column and Person allocating Parts can chose which ones.. but the Change Notice Reviewer has no idea if person picked correct one.  (we do not use CAD for Electrical Boards).  We would like it to display Reference Designator Information.


**********Business Case Downstream Usage**********

Reference Designators are used by various teams on during manufacturing:


We require the part number and reference designator link so that:


  • After loading a customer’s BOM information into our system we need to verify that the data loaded correctly:  To do that we export the BOM loaded from our system into an excel format and then compare it to the customers BOM information that they provided to us.  In that export we need the IPN, CPN and Reference designator.
  • We can produce an SMT program to populate a board:  Our SMT programmers require a report from Oracle that lists the part number, description and reference designator that the parts are placed at.  They combine this report with the CAD data from the customer in order to produce a Pick and Place program to populate the part on the boards. 
  • We can produce an assembly document:  Our assembly operators use assembly document / drawing that shows an outline of the product and a picture representation of the location a particular part is placed on the board.  This drawing shows the part number (Creation internal part number) and reference designators where a particular part is placed on the board.  The assembly document is produced by our teams using the cad data from the customer along with a BOM report that lists the part number and reference designator(s) for a particular part. 
  • All of our quality data tracking also has a link between the Part Number used and the Reference designator. 


In summary we require the part number and reference designator so that:


  • We can validate / verify that the information (BOM) we have in our system matches the customers BOM.  Part numbers and reference designators.
  • We can generate the automated programs necessary to build the products on the shop floor.
  • We can generate the documentation that is necessary internally to build the products to our customer requirements.
  • We can track quality data during production processes in order to analyze trends.