Amesim models in Teamcenter as CAE 1D objects

A .ame file becomes a managed Teamcenter object through the CAE 1D types that Teamcenter 2606 ships. Everything on this page was EXERCISED on 2026-09-24 against the local Teamcenter 2606 tier (vm2606) through the amesim MCP server, and then used by a second session to check in four QX-250 function models.

The object map, read from the tier

The types were confirmed with getTypeDescriptions2, with a made-up type name in the same call that correctly did not come back.

Role	Teamcenter type	Notes
1D model	CAE01DModel and CAE01DModelRevision	displayed as "CAE 1D Model"
1D analysis	CAE01DAnalysis and CAE01DAnalysisRevision	displayed as "CAE 1D Analysis"
The Amesim file	CAE0Amesim dataset	displayed as "CAE Amesim"
Where the .ame goes	named reference CAE0AME	other references: CAE0PCK (.pck), CAE0AMT (.amt), CAE0BAME (.bame), CAE0MISC, CAE0MISC-TEXT
Dataset to model	IMAN_specification	set in the same call that creates the dataset
Analysis to model	TC_CAE_Defining	the analysis revision is the primary object
Model to what it represents	TC_CAE_Source	the model revision is the primary; for example a Functionality
Analysis to what it analyses	TC_CAE_Target	the analysis revision is the primary; for example a logical block; more than one allowed

Corrected 2026-09-24: this page first said an analysis links to its model by TC_CAE_Source. That was wrong. Siemens' Amesim reference manual ("Manage CAE 1D analysis revision") says an analysis made in the context of a model is linked by the CAE Defining relationship; CAE Source links a CAE model to the product object it represents. The tools now write TC_CAE_Defining, and analyses 008538, 008543, 008545 and 008547 were given the Defining link. Their earlier Source links were left in place.

What the MCP tools do

Tool	What it does
amesim_tc_save_as	creates the model item, revision and dataset, uploads the .ame, optionally creates an analysis linked to it by TC_CAE_Defining
amesim_tc_find	finds CAE 1D items by name, with their datasets and links
amesim_tc_open	downloads the .ame; then amesim_open loads it in the solver
amesim_tc_checkout, amesim_tc_cancel_checkout	reserves or releases the dataset
amesim_tc_save	incremental save: uploads a new version of the dataset and leaves it checked out
amesim_tc_checkin	optional final save, then check-in

Authentication comes from the workspace's encrypted credential store through the Teamcenter MCP server's profiles, so no password is handled by the Amesim tools.

How a check-in is proven

A commit that reports nothing is the normal response, so the response is never the receipt. Each upload is checked three ways before the tool says it worked:

1. The dataset's file list, read fresh, carries the file name.
2. The stored file answers its file_size. A file that was never written to the volume fails here and names the missing path.
3. The file is downloaded again and its sha256 and byte count are compared with the local file.

Results so far

• Probe model 008537 and analysis 008538: dataset versioned from 1 to 4 by incremental saves, every version byte-verified; the downloaded file opened in the solver.
• QX-250 F1 battery model 008536 with analysis 008534, checked in by the Amesim UAV session, with its results file under CAE0MISC-TEXT.
• QX-250 F2, F4 and F10 models 008542, 008544 and 008546, checked in with amesim_tc_save_as; stored sha256 equal to local for all three.

Traps

• A null userData member makes createRelations fail with a server error. Leave the member out.
• Every property value comes back as a list. checked_out reads ['Y'] when reserved and [' '], a single space, when not. Comparing it as a single value always fails.
• Looking up something that is not an object id returns an empty object that looks found. A Teamcenter object id is 14 characters; anything else is treated as an item id.
• TC_CAE_Source from a model revision accepts only one secondary. A second one is refused with error 89009, which fits its meaning: a model represents one product object.

Not covered yet

Closed later on 2026-09-24: amesim_tc_revise makes a new model revision (A to B) for a design change. Teamcenter gives the new revision no dataset and no links, so the tool creates a fresh CAE Amesim dataset on it, uploads the model byte-verified, and copies the model's CAE Source link forward. Analyses are left pointing at the old revision on purpose. Exercised on the probe item; the local tier needed no release step first.

Updated later on 2026-09-24: results files now travel with the model. amesim_tc_save_as, amesim_tc_save and amesim_tc_checkin take extra_files, stored in the same dataset version as the .ame (text files under CAE0MISC-TEXT), each verified by its own sha256. The F2, F4 and F10 models each now hold their .ame, results JSON and run log in dataset version 2.