GET THE PLUGIN
Download the Capital ⇄ Teamcenter Plugin
One JAR gives Capital Systems Architect 2512 three Teamcenter-connected actions — Import from Teamcenter, a live Teamcenter Browser, and Publish to Teamcenter. This package is self-contained: it ships with a multi-domain sample so it demos standalone — no Teamcenter server, no network, and no credentials.
tc-service later with a two-line config change.What's in the box
| File | What it is |
|---|---|
plugins\XceleratorTcImport\capital-tc-import.jar | The plugin — all three actions — and a CLI |
plugins\XceleratorTcImport\bundle.json | The bundled demo dataset (a multi-domain vehicle program) |
plugins\XceleratorTcImport\tc-connection.properties | Config, file-mode by default (no backend) |
plugins\XceleratorTcImport\extras\jackson-*.jar | Runtime deps — Capital 2512's own Jackson copies |
plugins\CustomMenuConfiguration.xml | Registers the three custom-menu actions |
README.md · INSTALL.md · DEMO-SCRIPT.md | Overview, drop-in install, and a click-by-click demo talk track |
docs\exchange-format.md | The neutral JSON contract (v1.2) + an annotated config template |
Install
Copy two items into your Capital installation's plugins\ folder — below, <CapitalHome> is the Capital root that contains plugins\, lib\, and doc\:
plugins\XceleratorTcImport\ → <CapitalHome>\plugins\XceleratorTcImport\
plugins\CustomMenuConfiguration.xml → <CapitalHome>\plugins\CustomMenuConfiguration.xml
Then load the plugin: if Capital is closed, just start Systems Architect; if it's already open, System ▸ Plugin ▸ Reload All.
<menu> element:
<item name="Import from Teamcenter..." action="plugin:Java//com.xcelerator.capital.tcimport.plugin.TcImportAction"/>
<item name="Teamcenter Browser" action="plugin:Java//com.xcelerator.capital.tcimport.plugin.TcBrowserPanel"/>
<item name="Publish to Teamcenter..." action="plugin:Java//com.xcelerator.capital.tcimport.plugin.TcPublishAction"/>Verify it loaded: open a platform design, press the Space Bar and type Custom — Import from Teamcenter… and Publish to Teamcenter… should appear (also on the right-click menus). Open the Design Inspector and find the Teamcenter Browser tab. If the actions don't appear, confirm the extras\jackson-*.jar files came across — the plugin needs them at runtime.
Run the demo
The bundled sample is a small multi-domain vehicle program, so both electrical and fluid show up: a Body Control Module and Front Zone Controller on a Body CAN network, a Fuel Boost Pump and Reservoir on a fluid line, and the cross-domain edge where the BCM feeds power to the fuel pump — one object accountable in two domains at once. Full talk track: DEMO-SCRIPT.md in the download.
Design Inspector → Teamcenter Browser → Refresh. Expand the tree: components with ports and maturing parameters (the pump's flow rate shows a budget 40 l/min and a tested 42.1), functions and allocations, the CAN network, and requirement links.
Space Bar → Custom → Import from Teamcenter…. A dry-run preview appears first (nothing written). It matches components by TC_ID then name, syncs TC_DOMAIN / TC_PARAM_*, verifies functions and allocations, and writes every gap to a "Teamcenter Import" tab. It's idempotent — re-import updates, never duplicates.
Space Bar → Custom → Publish to Teamcenter…. The plugin walks the design into a Logical BOM v1.1 JSON in tc-outbox\ — open it to show components, carriers, signals, allocations, derived connections, and REQ_* links: the exact neutral contract.
Preview without Capital
The JAR is also a CLI, so you can show the pipeline on any machine with Java — run these from inside the plugins\XceleratorTcImport\ folder:
java -jar capital-tc-import.jar validate --file bundle.json
java -jar capital-tc-import.jar dry-run --file bundle.json
validate proves referential integrity; dry-run prints every operation a real import would perform.
Optional: live round-trip
To demo against a running Teamcenter-side service instead of the bundled sample, edit tc-connection.properties and Reload All:
tc.source=rest
tc.baseUrl=http://<service-host>:8080
publish.postEnabled=true
The Teamcenter Browser then reads live (falling back to the bundled sample if the service is unreachable), and Publish also POSTs the bundle. How the data model maps end to end is documented on the Teamcenter Data Model page; the full annotated config reference ships in the download at docs\tc-connection.sample.properties.