See the source relationships.
Bring the internal part and its manufacturer or vendor references into view when reviewing a component or product structure.
Secure Supply Chain CollaborationSource in context.
Source in context.
Share with control.
Connect the internal product definition with manufacturer and vendor records. Give sourcing decisions a clear context, and define how selected information reaches authorized partners.
Explore the sourcing exampleBring engineering and procurement around the same definitionOne product requirement.
One product requirement.
A clearer sourcing picture.
Supply-chain collaboration in PLM connects the product a team defines with the organizations and parts considered for its supply. Secure collaboration starts with an identified reference, maintained sourcing information and appropriate access to the records each participant needs.
- Internal partThe engineering reference
- The OEM part identifies the item your organization manages in the product structure. It provides the reference for associated supplier-part information.
- Manufacturer partThe item made by a manufacturer
- An approved manufacturer list (AML) relates manufacturer part records to the internal part. The maker’s identity and part reference remain distinct.
- Vendor partThe item offered by a seller
- An approved vendor list (AVL) relates vendor part records to the internal part. A vendor and a manufacturer are different roles, even when one organization performs both.
Give source decisions a visible place in product developmentBring choices forward.
Bring choices forward.
Keep decisions connected.
Maintained supplier relationships help engineering and sourcing discuss the same component. Their usefulness depends on accurate records, clear ownership and the context in which a part will be used.
Read the relevant preference.
Consider the status recorded for the relationship in the selected sourcing context, rather than assuming one preference applies everywhere.
Retain a useful record.
Keep supplier identities, part references and maintained sourcing information available to the people responsible for design and procurement decisions.
Make the next question clear.
Use the known product and sourcing context to identify what a buyer, supplier or engineering owner needs to review before acting.
Separate part identity from sourcing preferenceOne internal part.
One internal part.
Two sourcing contexts.
Compare two example contexts for the same panel connector and the same supplier-part records. A sourcing status belongs to the relationship with the internal part; a selected context can change which list and status apply.
Internal part · panel connector
Read the preference for early builds.
The prototype context records a preferred manufacturer relationship and an approved vendor relationship. The part identities remain separate from the preference used for this scope.
| Supplier-part record | List | Sourcing status | Meaning in this context |
|---|---|---|---|
| Manufacturer part M-01 | AML | Preferred | Preference for this manufacturer-part relationship in the prototype scope. |
| Vendor part V-01 | AVL | Approved | Status for this vendor-part relationship in the prototype scope. |
Which supplier-part relationships support the prototype sourcing discussion?
Review the production sourcing scope.
The production context retains the same supplier-part identities while recording different preferences. The buyer needs the applicable context and maintained status before interpreting the list.
| Supplier-part record | List | Sourcing status | Meaning in this context |
|---|---|---|---|
| Manufacturer part M-01 | AML | Approved | Status for this manufacturer-part relationship in the production scope. |
| Vendor part V-01 | AVL | Preferred | Preference for this vendor-part relationship in the production scope. |
Which context and maintained sourcing decision should this production discussion use?
Standard sourcing statuses include Preferred, Approved and Do Not Use. Their meaning is tied to the maintained relationship and context; they do not establish stock, price, delivery availability or engineering certification.
Connect the sourcing decision to a deliberate information handoffAgree the boundary.
Agree the boundary.
Give the response an owner.
Supplier records help explain what may be sourced. The exchange process defines which product information a participant receives, what action is permitted and who acts on the response.
Select the reference and permitted action.
Identify the records, versions and dependencies needed for the task. Review participant roles and object-level permissions for viewing, contribution or authoring; access to a supplier record does not grant unrestricted product access.
Explore collaboration solutionsRoute concerns to the responsible process.
Give supplier questions and quality concerns an owner. When a response calls for investigation or a product change, retain the sourcing context and connect it to the appropriate governed work.
Connect quality informationDefine the operational handoff.
Agree how the receiving purchasing or manufacturing environment uses the selected definition. Interfaces, mappings, refresh expectations and ownership determine the connection to operational systems.
Explore manufacturing contextWindchill Supplier Management is intended for a configured PDMLink environment, with supplier organizations, roles, attributes and permissions defined for the work. Confirm the required release, applications and licenses; a standalone ProjectLink workspace is a different scope.
Explore WindchillMake the first sourcing conversation specificChoose one component.
Choose one component.
Clarify its supply context.
Bring TriStar an internal part with a real sourcing question. Use it to agree the records, decisions and information exchange a first phase should support.
The component and references
Identify the internal part, relevant product structure, manufacturer and vendor part information already held by the team.
The context and ownership
Describe where sourcing preferences differ and who maintains the relationships, supplier records and decisions.
The first exchange
Choose one buyer or supplier task, the product information needed, the permitted response and the system or owner receiving it.
Apply the discipline to a real product situationDifferent supply networks.
Different supply networks.
A shared sourcing reference.
A useful supplier handoff has a defined information scope and a recognizable product reference. Start with the relationship the receiving organization needs to evaluate.
Electronics & High-Tech
A component supplier may contribute manufacturer references and supporting documents. Keep the internal part identity distinct from the supplied item’s identity.
Which internal and manufacturer references must the team reconcile?
Aerospace & Defense
A program supplier needs the appropriate product configuration and agreed deliverables. Establish the shared context without assuming access to the complete program record.
What information and response belong within this supplier’s scope?
Industrials
A machine manufacturer may evaluate alternative supplied components across several assemblies. Make the proposed source and affected product relationships visible for review.
Which assemblies depend on the source being evaluated?
Clarify the supplier-data and exchange scopeSourcing questions.
Sourcing questions.
Separate records, access and decisions.
Use the first component to resolve the details that affect setup, interpretation and partner participation.
Does Approved mean the part is available to order?
Approved is a sourcing status for a supplier-part relationship in a context. Availability, price, purchasing terms and delivery commitments belong to the relevant commercial and operational processes. Confirm those separately before making a purchasing decision.
Is sourcing status a single rating for the supplier?
No. The status applies to the relationship between a supplier part and the internal OEM part, and it can differ by sourcing context. A general supplier record and a particular part relationship carry different information.
Can an external supplier change our internal product definition?
The permitted actions depend on the configured application, participant role and object permissions. Maintaining supplier information or receiving selected product data does not automatically grant authoring or release rights over the internal definition.
What needs to be configured for AML and AVL work?
Review Supplier Management within the PDMLink environment, the supported release, supplier organizations, part attributes, sourcing contexts and assigned administrative roles. Modification permissions and checkout rules also matter; this is not assumed functionality in every installation.
Will PLM keep ERP stock and planning data synchronized?
A supplier-data model does not establish an operational integration by itself. Define the supported records, interfaces, mappings, refresh rules and system responsibilities for the intended connection. Purchasing and planning information should retain its agreed system ownership.
Connect product intent to a practical supplier conversationBring the sourcing question.
Bring the sourcing question.
Build the shared reference.
Show us where engineering, procurement and partner information become disconnected.
We’ll help frame the supplier records, sourcing context and controlled exchange around the work your team needs to do.