tcli

Why tcli

Teamcenter does not define a standard structure for configuration and customisation projects. Repositories tend to grow organically: configuration files become scattered, build logic is duplicated, customisation libraries are difficult to compile consistently, and setting up even a simple import or deployment script can take significant effort.

tcli provides a unified management interface for Teamcenter configuration and customisation repositories. It establishes a predictable project structure, standardizes common build and deployment operations, and makes scripts and build failures easier to inspect and debug.

tcli itself contains no Teamcenter-project-specific content: no customisation libraries, BMIDE project, or declarative configuration. Everything project-specific remains in the repository where tcli is executed, controlled by that repository’s .tcli.yaml manifest and by tcli’s embedded, version-keyed catalog of scripts and templates.

The result is a consistent interface across Teamcenter projects. Whether deploying a workflow, exporting configuration, running administrative scripts, or building a customisation library, the command and project model remain the same.

Two surfaces, one engine

The TUI and the headless CLI call the exact same underlying functions. Neither is a superset of the other.

Guided TUI

A full-screen, keyboard-driven interface for interactive work. Configure your environment and navigate Add / Deploy / Export.

Scriptable CLI

Streams stdout/stderr straight through and mirrors the child process’s exit code, for CI and automation.

Version-keyed catalog

Scripts and templates are keyed by Teamcenter release, so scaffolding matches the version you target.

Next steps

Install

Build tcli from source with Go 1.25+.

Quick start

Initialize a project and create your first acrtifact.

Understand the model

Learn about the two-surface architecture and the project manifest.

CLI reference

Browse every subcommand and flag.