Streamline workflows by sending Bill of Materials (BOMs) data from Teamcenter to your Builds Parts & Assemblies.

Sync Teamcenter parts and multi-level bills of materials into Epsilon3 Builds so manufacturing teams can work from the same controlled product structure used by engineering.

The Epsilon3 Teamcenter integration connects product data managed in Siemens Teamcenter with the Parts area in Epsilon3 Builds. A configured Teamcenter workflow sends an item revision to Epsilon3, where Epsilon3 creates or updates the corresponding part record and reproduces the assembly’s component hierarchy.

Imported assemblies can then be used alongside Epsilon3 inventory, work instructions, attachments, usage records, and other manufacturing data.

When an assembly is submitted through the configured Teamcenter workflow, Epsilon3 receives the part and bill-of-material information required to recreate that product structure. The demonstrated transfer includes the Teamcenter item identifier, part or assembly name, revision, parent-child component relationships, and the quantity of each component in its parent assembly.

The result is not a flat list. Epsilon3 preserves the multi-level structure of the assembly, so subassemblies can be expanded to reveal their own children. Each imported item also becomes an individual Epsilon3 part record that can be opened directly from the assembly hierarchy.

Confirm that the Teamcenter integration is enabled for your Epsilon3 workspace and that the workflow used to send data to Epsilon3 is available in Teamcenter. You must also have permission to view the Teamcenter item revision, open its structure, and submit it to a workflow.

Before transferring an assembly, review its structure in Teamcenter. Verify that the intended item revision is selected, that the bill of materials contains the correct children, and that component quantities are accurate. Epsilon3 reproduces the structure submitted from Teamcenter, so errors in the source assembly should be corrected before the workflow is started.

Open the item revision that you want to send to Epsilon3. In the demonstrated workflow, the selected top-level item is an Engine Assembly item revision.

Use Teamcenter’s structure or bill-of-material view to inspect the assembly before submission. The structure view lists each immediate child of the selected assembly and shows information such as the item type, quantity, and reference designator. Expanding the structure displays lower-level parts and subassemblies.

From the Teamcenter item revision, open the Actions menu and select the command to submit the object to a workflow.

Teamcenter opens the Submit to Workflow panel with the selected item revision included as the workflow target.

Choose the workflow template configured for the Epsilon3 integration. The template name is determined by your Teamcenter administrator. Add a description when your organization uses workflow descriptions to identify or audit transfers.

Review the Targets section and confirm that the correct assembly revision is listed. The top-level revision selected here determines which assembly structure is sent to Epsilon3. Select Submit to start the workflow.

After submission, Teamcenter displays a confirmation that the item revision was submitted to the workflow. The integration then processes the selected revision and its structure. Processing time can vary with the size of the assembly and the integration environment.

In Epsilon3, open Builds and select Parts. The Parts page contains the individual part and assembly records available in the workspace.

After the Teamcenter workflow completes, the transferred records appear in the list.

Each row shows the imported part identifier, revision, and current inventory information. The top-level assembly and its imported child items are available as separate records because each may be referenced independently in Epsilon3.

Select the top-level assembly from the Parts list to open its part record. The header identifies the imported part number and assembly name, while the revision badge shows the Teamcenter revision associated with the record.

The part page also provides Epsilon3-native areas for information that may be managed during manufacturing, including tags, inventory state, attachments, work instructions, usage, comments, and components.

An imported Teamcenter record can therefore serve as the controlled product definition while Epsilon3 holds the operational information used to build and track it.

The tabs in the part header separate inventory into In Inventory, Scrap, and Unavailable states. A newly imported part may display zero inventory because the Teamcenter transfer creates the product record and structure; it does not represent a physical stock transaction.

Use Add Tag to classify the part in Epsilon3. Attachments, work instructions, and usage records can also be added when these are needed by the manufacturing team.

These sections are shown independently from the imported component structure, allowing teams to enrich the Teamcenter-defined part without changing its identity or bill of materials.

Scroll to Components to review the assembly structure imported from Teamcenter.

Each component row shows the child part number, child name, revision, and quantity required by the parent.

Select the arrow beside a subassembly to expand it. Epsilon3 displays the subassembly’s children directly below it, preserving the multi-level hierarchy from Teamcenter. Continue expanding nested assemblies to trace the product structure from the top-level assembly down to lower-level parts.

The Components section reproduces the imported hierarchy and the quantity of each direct child.

Expand a subassembly to inspect its lower-level components without leaving the parent assembly.

The revision shown in Epsilon3 corresponds to the Teamcenter item revision transferred by the workflow. Always confirm the revision before using an imported part for production, especially when multiple revisions of the same item exist in Teamcenter.

Treat Teamcenter as the source of truth for controlled part identity, revision, and bill-of-material structure. Review and release product changes in Teamcenter before submitting them to Epsilon3, and avoid manually recreating the same assembly structure in Epsilon3 unless your process specifically requires it.

After each transfer, verify the top-level revision, inspect several component quantities, and expand at least one nested subassembly. For large assemblies, use the Parts search field to confirm that representative lower-level components were also created.

Use Epsilon3 for the operational context surrounding the imported product definition, such as inventory status, work instructions, attachments, usage, tags, and comments.

Confirm that you opened the correct Teamcenter item revision and that your account has permission to use the integration workflow. If the template is still missing, contact the Teamcenter or Epsilon3 integration administrator.

Confirm that Teamcenter reported a successful workflow submission. Allow time for the workflow and integration processing to complete, then refresh Builds > Parts and search for the exact Teamcenter item identifier. If the record is still missing, provide the item identifier, revision, workflow name, and submission time to your administrator.

Return to Teamcenter and verify that the missing items were part of the submitted revision’s structure. Confirm that the correct revision was selected as the workflow target and that the Teamcenter structure was fully saved before submission.

Compare the quantity in Epsilon3 with the quantity in the Teamcenter structure for the submitted revision. Correct source bill-of-material data in Teamcenter and follow your organization’s approved process for retransferring the assembly.

This is expected when no physical inventory has been recorded in Epsilon3. The Teamcenter workflow creates the product record and assembly structure; inventory quantities are managed separately in Epsilon3.