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

We are happy to announce the new Windchill Customization board! Learn more.

CAGE Codes & CAD Document Uniqueness

thomas_hogan_99
1-Newbie

CAGE Codes & CAD Document Uniqueness

All,

From what I understand, CAD (EPM) Documents in PDMLink must be unique by filename and number across
the database. The CAGE Code (or WTOrganization Object) value has no impact of uniqueness. We have the
Aerospace and Defense module installed, but it doesn't seem to work for CAD Documents. Wondering if somebody
is doing something clever of if we have missed something here.

If you're not familiar with CAGE Codes, their purpose is to help identify parts from different vendors but with
the same part number, unique.

Wondering how y'all handle conflicts that would otherwise be avoided were the CAGE Code actually make
files unique? If you have to make rename the filename and/or number, kind of makes the CAGE Code useless, doesn't it?

Thanks in advance!

Tom Hogan
thomas_hogan@verizon.net

5 REPLIES 5

Try this,

Looks like this will be fixed in 9.1 M050

https://www.ptc.com/appserver/cs/view/spr.jsp?n=1846564

I would like to know if this solution would apply for multiple CAD and would allow the user of MPMLink and document creation to accidentally select the CAD ORGID for the ORGID of the Part and Document since orgid's are searchable from the user and will be confused with all the CAD types. This has been proposed at other customers, but they said that the ORGID was not to be mixed with CAD types. So, we went with the solution of just applying new indexes which does not require creating fake org id's for cad types. Architectually it was a bad solution creating more data to represent the data already in the EPMDOCUMENTMASTER table. Some companies actually have contract engineering manufacturers checking into their work into different organizations contexts which is tied to different org id's. Thus, the data is placed according to the correct meaning of information. This solution from PTC sounds very limited and not scalable. Like I said, try out the solution from the powerpoint. It will not cause confusion to your users and keep data where they are supposed to be architectually.

Using ORGID will cause confusion:
- in MPMLINK,selecting CAD types for creating vendors and manufacturers from the supplier ADMIN.
- Admins are allowed to create, modify, DELETE ORGIDs on the fly if not tied to any object (hopefully)
- ORGIDs are searchable from the search and you have to group/separate the CAD types from the other valid ORGIDs.
- the ORGIDs solution as CAD types is just a poor unrefined solution using the wrong attributes to represent another.
- You should really try the new indexes and it doesn't cause confusion. You can now package everything by number.


In Reply to Tom Hogan:

From the BINCS website https://www.bpn.gov/bincs under FAQs:

"A CAGE Code is a five (5) position code that identifies companies doing or wishing to do business with the Federal Government. The format of the code is the first and fifth position must be numeric. The second, third and fourth may be any mixture of alpha/numeric excluding I and O. All positions are non-significant."

"The code is used to support a variety of mechanized systems throughout the government. The code provides for a standardized method of identifying a given facility at a specific location. The code may be used for a Facility Clearance, a Pre-Award survey, automated Bidders Lists, pay processes, source of supply, etc. In some cases, prime contractors may require their sub-contractors to have a CAGE Code also."

Depending on how unique a number should be, the same manufacturer's part number could be linked to any number of CAGE Codes - Sherwin- Williams has over 1200 because the US Government often buys its paint locally.

The DOD side often uses the CAGE Code of the facility they contract with, such as the corporate offices, but suppliers sometimes mark the parts with the CAGE Code where the item is fabricated, which is subject to change.

Top Tags