Supplier Collaboration Foundation or Partner Connect — Which One Is Right for Your Organisation?

Introduction: Managing Supplier Collaboration in Teamcenter

Modern manufacturing organisations rarely develop products in isolation. From component suppliers to contract manufacturers and Tier-2 partners, the product development lifecycle involves a complex web of external stakeholders — each needing timely, accurate access to product data.

Managing that external data exchange through email, FTP, or disconnected portals introduces version control risk, security vulnerabilities, and significant process overhead. Teamcenter addresses this challenge with a dedicated supplier collaboration framework built on top of its Vendor Management capability — giving OEMs structured, controlled mechanisms to share product data with external parties without compromising PLM data security or integrity.

This article explains how Teamcenter enables supplier and vendor collaboration through two primary modules — Supplier Collaboration Foundation (SCF) and Partner Connect — and provides practical guidance on when to use each.

Teamcenter Vendor Management: The Foundation

Both the Supplier Collaboration Foundation and Partner Connect modules are built on top of Teamcenter's Vendor Management feature. This foundational layer provides the mechanisms for:

Managing data and business processes associated with suppliers and vendors
Tracking changes to vendor and parts information over time
Maintaining supplier master data within the Teamcenter data model
Associating vendor-specific contracts, documents, and lifecycle states with product data

Understanding the Vendor Management layer is essential before configuring either collaboration module, as the underlying data structures and access control models inherit from it.

Teamcenter Vendor Management architecture showing SCF and Partner Connect sitting on top of the Vendor Management foundation layer — Figure 1: Teamcenter Vendor Management architecture — showing how SCF and Partner Connect sit on top of the Vendor Management foundation layer, with supplier data structures and access control inherited from it.

Option A: Teamcenter Supplier Collaboration Foundation (SCF)

Supplier Collaboration Foundation (SCF) is designed for scenarios where an OEM needs to exchange product data with external suppliers who do not have, and do not need, a full Teamcenter account. It provides a lightweight, event-driven model for data exchange.

Option A

Supplier Collaboration Foundation

Event-Driven Exchange

How SCF Works

SCF provides a dedicated, separate client application for suppliers. The OEM creates a data exchange event and sends an invitation to the supplier. The supplier receives an email containing credentials and a URL, logs into the SCF client, and interacts with the shared data — without ever accessing the OEM's Teamcenter environment directly.

SCF data exchange flow showing OEM creating exchange package in Teamcenter, invitation email sent to supplier, and supplier accessing shared data via SCF client — Figure 2: SCF data exchange flow — OEM creates exchange package in Teamcenter, invitation email is sent to supplier, supplier logs into SCF client and accesses shared design data or bid package.

Primary Use Cases for SCF

1. Design Data Exchange — The OEM shares design data for contract manufacturing or review. An exchange package is created in Teamcenter and sent to the supplier. The supplier can view attributes, BOM structures, and CAD files, and submit review inputs back to the OEM. This is the most common SCF use case in automotive and industrial equipment manufacturing.

2. Bid Processing — The OEM distributes a work package to multiple suppliers for competitive bidding. Each supplier logs into the SCF client, reviews the package specifications, and submits their bid. This centralises bid management within the PLM environment, giving procurement teams a single view of all responses.

Offline Data Exchange via Briefcase Browser

In some environments, network restrictions or supplier firewall policies prevent direct URL access to the SCF client. Teamcenter addresses this through the Briefcase Browser application. The OEM can package and share design data — including attributes, BOM structures, and CAD files — via a secured, password-protected email attachment. The supplier uses the Briefcase Browser locally to open and interact with this data.

This approach is particularly useful when working with smaller suppliers who lack the IT infrastructure to support direct system integration.

Briefcase Browser offline exchange showing OEM packaging design data as password-protected archive for supplier to browse locally without VPN — Figure 3: Briefcase Browser offline exchange — OEM packages design data as a password-protected archive, supplier opens and browses it locally using Briefcase Browser without requiring VPN or direct Teamcenter URL access.

Option B: Teamcenter Partner Connect

Partner Connect is designed for deeper, ongoing collaboration with strategic suppliers and partners. Unlike SCF, it does not provide a separate client. Instead, the vendor is given a full Teamcenter account and accesses product data directly through Active Workspace (AW) using the standard OEM URL.

This makes Partner Connect better suited to scenarios where collaboration is continuous rather than event-driven — for example, a Tier-1 supplier who is co-developing subassemblies, participating in change management processes, or needs to maintain their own documentation within the OEM's PLM environment.

Option B

Partner Connect

Deep Integration

How Access Control Works in Partner Connect

Because vendors access the same Teamcenter environment as internal users, robust access control is essential. Partner Connect uses a Partner Contract object — a dedicated Teamcenter business object — as the mechanism for governing what shared data a vendor can see and interact with.

Every object shared with a vendor has a Partner Contract attached to it
The contract defines which data the vendor can access and at what privilege level
Access is time-bound — an end date is mandatory on the contract, preventing indefinite data exposure
When the contract expires, the vendor's access to that data is automatically revoked

This model gives the OEM fine-grained, auditable control over external data access — an important requirement in regulated industries such as aerospace and defence where IP protection and supplier data governance are subject to compliance audits.

Partner Connect access control model showing Partner Contract object attached to shared Teamcenter objects with time-bound access settings and automatic expiry — Figure 4: Partner Connect access control model — Partner Contract object attached to shared Teamcenter objects, showing time-bound access settings, privilege levels, and automatic expiry behaviour in Active Workspace.

SCF vs Partner Connect: Side-by-Side Comparison

The table below summarises the key differences between the two modules to help you select the right approach for a given supplier relationship:

Criteria	Supplier Collaboration Foundation	Partner Connect
Client Access	Separate SCF client (no TC account needed)	Active Workspace (full TC account)
Collaboration Depth	Loosely coupled — data exchange events	Tightly coupled — live object access
Access Control	Invitation-based per event	Partner contract object with time-bound expiry
Primary Use Cases	Design Data Exchange, Bid Processing	Change management, documentation, full BOM collaboration
Offline Data Sharing	Briefcase Browser via secure email	Not applicable — online access only
Setup Complexity	Lower	Higher — requires TC user provisioning
Best For	External suppliers with no TC licence	Strategic partners requiring deep integration

Choosing the Right Module: Decision Guidance

The choice between SCF and Partner Connect is driven by the nature of the supplier relationship and the depth of collaboration required. Consider the following factors:

Use Supplier Collaboration Foundation when:

The supplier has no Teamcenter licence and you do not want to provision one
Collaboration is event-driven rather than continuous — individual design packages, bid events
You need a lightweight, low-overhead way to exchange data with a large number of suppliers
Network or IT constraints prevent direct system access for the supplier

Use Partner Connect when:

The supplier is a strategic partner involved in co-development or ongoing change processes
You need the vendor to participate directly in Teamcenter workflows — change notices, approvals, documentation
You require time-bound, contract-governed access with full audit traceability
The supplier already has Teamcenter capability internally, making provisioning straightforward

Implementation Considerations

Before configuring either module, there are several practical factors that implementation teams should address:

Note: These considerations apply regardless of which module you select. Address them during the design phase — retrofitting access control and data classification decisions after go-live is significantly more disruptive.

User provisioning and licensing Partner Connect requires a Teamcenter user licence for each vendor user. Plan for this in your licensing model. SCF does not require additional TC licences for suppliers.

Data classification Determine upfront which product data is safe to share externally. Establish a classification scheme — for example, Internal, Restricted, Shareable — within the Teamcenter data model before enabling external access of any kind.

Partner Contract lifecycle management For Partner Connect deployments, define an operational process for creating, reviewing, and expiring Partner Contracts. Contracts without a managed lifecycle can result in stale vendor access persisting well beyond the intended collaboration period.

Briefcase Browser deployment If SCF offline exchange is required, Briefcase Browser needs to be distributed to suppliers. Establish a version management process to ensure suppliers are always on a compatible version relative to your Teamcenter environment.

Network and security SCF client access is URL-based and must be reachable from the supplier's network. For suppliers behind strict firewalls, the Briefcase Browser approach may be the only viable option. For Partner Connect, ensure Active Workspace is accessible externally — typically via HTTPS with a valid SSL certificate.

Summary

Teamcenter provides a mature, well-structured framework for supplier and vendor collaboration through two complementary modules — Supplier Collaboration Foundation for lightweight, event-based data exchange, and Partner Connect for deep, ongoing collaboration with strategic partners.

Both modules are built on the Vendor Management foundation, which provides consistent supplier data management, access control, and lifecycle tracking across the platform. Selecting the right module depends on the nature of the supplier relationship, the depth of required collaboration, and the IT capabilities of the vendor.

For implementation teams, the key success factors are clear data classification, disciplined Partner Contract lifecycle management, and a deliberate approach to supplier onboarding — whether through the SCF client or Active Workspace direct access.

Key Takeaways

Both SCF and Partner Connect are built on Teamcenter Vendor Management. Understand the foundational layer before configuring either module — the data structures and access control model flow down from it.
SCF is the right choice for event-driven, loosely coupled collaboration. If the supplier does not need a Teamcenter account, SCF handles design data exchange and bid processing without provisioning external users.
Partner Connect suits strategic, ongoing supplier relationships. When a Tier-1 partner needs to participate in workflows, change management, and live BOM access, Partner Connect's Active Workspace-based model is appropriate.
The Partner Contract object is the core access control mechanism in Partner Connect. Every shared object requires a contract with a mandatory end date — without disciplined contract lifecycle management, stale vendor access accumulates.
Briefcase Browser extends SCF into restricted network environments. For suppliers behind strict firewalls, password-protected offline data packages replace direct URL access — but version alignment between OEM and supplier must be actively managed.
Data classification must precede external access configuration. Defining what is shareable, restricted, and internal at the data model level is a prerequisite — not an afterthought — for any supplier collaboration deployment.