Verified Teamcenter business-object type atlas

Every type below was confirmed against a live TC 2506 BMIDE, most by creating an instance and reading it back. Types marked does not exist were plausible guesses that turned out to be wrong, and are listed so nobody re-guesses them.

Ground new types against saberdatamodel.xcelerator.us (public/models/saber-2.0/objects.json, 8,571 objects with inheritance) rather than by trial and error. That technique took a domain crack from roughly 50 blind attempts to first-or-second-try on every call.

Systems architecture

Role	Item	Revision	Parent	Notes
Function	Functionality	FunctionalityRevision	Fnd0SEBlock	Fnd0Function does not exist
Logical block	Fnd0LogicalBlock	Fnd0LogicalBlockRevision	Fnd0SEBlock
Signal	Signal	SignalRevision	PSSignal	className returns PSSignalRevision. Fnd0Signal does not exist
Network	Network	NetworkRevision	PSConnection
Interface spec	Seg0IntfSpec	Seg0IntfSpecRevision	Item	What an in-model Cameo Signal lands as
Logical connector	Fnd0LogicConn	Fnd0LogicConnRevision	PSConnection
Interface / port	Fnd0LogicIntrfce	-	Interfaces > GeneralDesignElement > Form	Not independently creatable (Form family)

Cameo-side landing shape, measured: the two-hop GRM path Seg0Interface --Seg0ExchangeAllocation--> Seg0ItemFlow --seg0ExchangeItem--> Seg0IntfSpec. The Seg0ItemFlow is the flow property (seg0Kind='FlowProperty', seg0Direction='fnd0Output'|'fnd0Input'). Carriers are Seg0ItemFlowExchanges objects reached by Seg0HasExchangeItem.

Requirements

Role	Type
Requirement	Requirement / Requirement Revision
Specification	RequirementSpec / RequirementSpec Revision

Arm0RequirementSpecElement and Arm0RequirementElement are real, but they are occurrence / BOM-line VIEW types, not persistent item types. They appear in OccurrenceManagement calls and AWC URLs as runtime SR::N::... uids. A type query against them returns 0 because you are querying a persistent-object store for a runtime view type. Both layers are real.

Verification and test

The real packages are iav0verificationmanagement (167 objects, "Integrated Analysis & Verification"), crt0validationcontract (77 objects, the request / contract container) and the simpler independent tm0tsm ("Test Manager", 20 objects).

Role	Type
Verification Request (umbrella)	Crt0VldnContract / Crt0VldnContractRevision
Simulation Request	IAV0SimulRequest / IAV0SimulRequestRevision
Test Request	IAV0TestRequest / IAV0TestRequestRevision
Test Case	IAV0TestCase / IAV0TestCaseRevision
Test Procedure	IAV0TestProcedur / IAV0TestProcedurRevision
Test Event	IAV0TestEvent / IAV0TestEventRevision
Verification Requirement	IAV0VerifReqmt (a Requirement subtype)

Specializations of Crt0VldnContract: Crt0VerifRequest (physical/instrumented), Crt0Test (basic, RM-driven), Crt0Study / Crt0SimStudy (scoped studies), Crt0Run (generic execution / results capture).

IAV0VerifAssmForm is the Form where the verification method and result are literally recorded; both IAV0TestCaseRevision and IAV0VerifReqmtRevision attach to it via IAV0VerifReqAssmFormRel. Forms need a different attach pattern than createAttachAndSubmitObjects plus createRelations.

"VCRM" (Verification Cross-Reference Matrix) is NOT a stored TC type anywhere in the 8,571-object catalog. It is a report over the requirement-to-testcase links.

A large bespoke package (xve5xceleratormbse, 601 objects, a flight-test vertical) extends IAV0TestCase and Crt0Run directly, which is evidence those are the sanctioned Siemens extension points rather than customer inventions.

Simulation and reliability

Role	Type	Parent chain
Simulation analysis	CAEAnalysis / CAEAnalysisRevision	CAEItem > Item
FMEA failure mode	Mq0FailureMode / Mq0FailureModeRevision	Item
FHA failure condition	Fha0FailureCndn / Fha0FailureCndnRevision	Fha0FHARoot > Item

IAV0SimulRequest and CAEAnalysis are genuinely separate objects: the request to perform verification by analysis, versus the analysis itself. The only GRM bridge is CAE0Correlation (CAE0PhTestResultRevision to CAEAnalysisRevision/CAEResultRevision), which correlates results after the fact, not the request objects.

Mechanical

Role	Type
Design	Design / Design Revision
Generic baseline	Item / ItemRevision

Design is more specific but Item remains the safer already-GRM-confirmed baseline for IMAN_specification plus UGMASTER work.

Electrical / Capital: the package is HRN, not "Capital"

No Cap0, ELC0 or Capital-branded BMIDE package exists. (cpa0capadatamodel is a false positive: that is Quality CAPA, Corrective and Preventive Action.) Capital's Teamcenter surface is the hrn template, in two layers.

Layer 1, HRN_*, the physical part catalog (17 Item-rooted independently creatable types):

Group	Types
Assembly	HRN_Harness
Conductors	HRN_Cable, HRN_GeneralWire, HRN_Core (Form-only)
Connectors	HRN_ConHousing, HRN_Cavity (Form-only), HRN_Slot (Form-only), HRN_GenTerminal
Sealing / protection	HRN_CavityPlug, HRN_CavitySeal, HRN_Shield, HRN_WireProtect
Mounting / supplementary	HRN_Fixing, HRN_Accessory, HRN_AssemblyPart, HRN_CoPackPart

A populated "connector" is housing plus cavities plus terminals.

Layer 2, Hmc0*, the project / design container layer: Hmc0Project (root Electrical Project) holds the Hmc0AbsDesign family (Hmc0Design, Hmc0FunctionDes, Hmc0HarnessDes, Hmc0LogicDesign, Hmc0TopologyDes, Hmc0PlatformDes, Hmc0IntegDes, one per authoring discipline) and a parallel Hmc0AbsBuildList family (the manufacturing counterpart). Each carries native datasets: Hmc0DesignXML (almost certainly the literal Capital Harness XC import/export payload), Hmc03DHarness, Hmc03DWiring, Hmc0NXDataset. Hmc0Cable subtypes HRN_Cable directly.

Critical caveat: none of these 31 types appear anywhere in the 1,952-row GRM table as primary or secondary. This model is a GRM island. FND_TraceLink from HRN_Cable Revision to SignalRevision nonetheless works live. Empirical success is the stronger evidence; just do not assume GRM backs it.

Rejected, informative: SKW9_*/SKW5_* ADP customer-template electrical parts (zero GRM connections, bespoke sample config); Mfg0Cable (plant/robot cabling, not product harness); the NXP0Equipment family (P&ID piping); Eml0ResConnector and Seg0OpConnector (DoDAF enterprise/operational architecture). RouteSegment/RouteNode are referenced in HRN relation descriptions but absent from both the object catalog and the GRM table.

Parameters

Tier	Types
Definition	Att0AttributeDef / Att0AttributeDefRevision
Parameter instance	Att0MeasurableAttribute{Dbl,Int,Str,Bool,Pnt}
Measurement	Att0MeasureValue{Dbl,...}
Unit	UnitOfMeasure (has no object_name, so type queries return 0)

See ../skills/tc-parameters-units/SKILL.md.

Program planning / IPP&E

Confirmed deployed and Item-rooted (so they create through the ordinary createAttachAndSubmitObjects engine): Wbs0Root, Wbs0Element, Psi0WorkElement, Prg0ProgramPlan, Ipp0IPT.

Known gaps: Ipp0IMPAccomplishment requires an "IMP Element ID" property whose real internal name is unknown (ipp0IMPElementID is wrong; the create-input descriptor is Ipp0IMPAccomplishmentCreI). Prg0ProgramPlan faults "invalid input object" through plain createAttachAndSubmitObjects; Program Planning has its own create flow.

Structure / occurrence types

Type	Notes
BOMLine	The occurrence view type returned by structure expands
GDELine	Base BOMLine; port occurrences are this type, and carry fnd0bl_connected_end1, fnd0bl_connected_end2, bl_connected_to_absName
Awb0ProductContextInfo	The product context BOMLine used by AW occurrence operations
ImanRelation	A relation's own object; getProperties on its uid names both endpoints
ImanQuery	A saved query object

Modules that are genuinely not installed everywhere

Mdc0ConnectionElement (TC's MDConnectivity module) did not exist per getTypeDescriptions2 on one 2506 tier, despite Mdconnectivity-2014-10-MDConnectivity matching the need by name and struct shape. That is a real negative, established with a type check rather than a fault code. Establish absence that way, never from a fault code.

---

Generated from references/type-atlas.md in the tc-automation-skills library, which is the canonical copy and also serves as the agent skill set for Teamcenter work.