{
 "categories": [
  "engineering",
  "enterprise",
  "document-control"
 ],
 "deployment": "hybrid",
 "evidence": [
  {
   "date": "2026-09-09",
   "fact": "homepage",
   "note": "Siemens presents Teamcenter as PLM software to plan, develop, and deliver products, with Teamcenter AI and Teamcenter Copilot, and names Northrop Grumman as a customer.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "deployment",
   "note": "The product page offers Teamcenter on premises, on a customer-managed cloud, and Teamcenter X as SaaS operated by Siemens.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "deployment",
   "note": "Siemens presents Teamcenter X as SaaS delivery of the full Teamcenter PLM portfolio on the cloud, operated by Siemens, not as a second product identity.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/teamcenter-x-cloud-plm/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "platforms",
   "note": "Siemens describes Active Workspace as an HTML5, zero-install client used from a web browser, including on mobile devices, and as the preferred client for cloud Teamcenter.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-active-workspace-strategy/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "license",
   "note": "The page offers plans and pricing and a contact path. Teamcenter is sold as commercial PLM, not a public free tier.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "status",
   "note": "Siemens markets Teamcenter as a current PLM suite and cites the 2026 Gartner Magic Quadrant for PLM software.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.api.exists",
   "note": "Siemens states that Teamcenter documentation includes full API references for the Integration Toolkit (ITK) and SOA service bindings, updated each release, and points at Teamcenter 2606 documentation.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.api.kinds[0]",
   "note": "The opened Siemens blog names SOA service bindings as a first-party Teamcenter API surface alongside ITK.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.api.coverage",
   "note": "Siemens Industry Software's Mendix docs state that Teamcenter Connector reads, creates, and modifies Teamcenter product data. Public HTML still does not publish the SOA endpoint catalog or authentication contract, so coverage stays partial.",
   "source": "https://docs.mendix.com/appstore/industry/teamcenter-connector/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.api.docs",
   "note": "This Siemens blog is the public page that declares current ITK and SOA API references. The documentation home page itself is reached through Support Center.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.sdk",
   "note": "Teamcenter Connector for Mendix is official Siemens Industry Software documentation. Connector services are Java actions. Minimum Teamcenter is 2406; minimum Teamcenter X is 2506.",
   "source": "https://docs.mendix.com/appstore/industry/teamcenter-connector/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.sdk.languages[0]",
   "note": "Mendix docs state that Teamcenter Connector services are provided through Java actions and that Active Workspace SOA API documentation is generated with genSoaApi.",
   "source": "https://docs.mendix.com/appstore/industry/teamcenter-connector/references/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.mcp.first_party",
   "note": "Opened Siemens Teamcenter documentation and product pages name ITK, SOA, Active Workspace, and Teamcenter AI/Copilot. They do not declare a first-party MCP server for Teamcenter, so ownership stays unknown.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.mcp.third_party[0]",
   "note": "Opened GitHub repository titled SIEMENS Teamcenter Model Context Protocol (MCP) Server. It is third-party, not a Siemens-declared official server.",
   "source": "https://github.com/goenninger-b-t/tc-mcp",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.mcp.third_party",
   "note": "Official MCP registry search for teamcenter returned {\"servers\":[],\"metadata\":{\"count\":0}}. Registry silence is not proof that Siemens ships no first-party server.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=teamcenter",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.integrations.zapier",
   "note": "Zapier's public app directory returned 404 for teamcenter on 2026-09-09.",
   "source": "https://zapier.com/apps/teamcenter/integrations",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.integrations.make",
   "note": "Make's app catalogue rendered a coming-soon 404 for /teamcenter on 2026-09-09.",
   "source": "https://apps.make.com/teamcenter",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.integrations.power_automate",
   "note": "Microsoft's connector path /connectors/teamcenter/ returned 404 on 2026-09-09.",
   "source": "https://learn.microsoft.com/en-us/connectors/teamcenter/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.integrations.n8n",
   "note": "n8n's built-in app-node documentation returned page-not-found for n8n-nodes-base.teamcenter on 2026-09-09.",
   "source": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.teamcenter/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Siemens names the Integration Toolkit (ITK) among the full API references in Teamcenter documentation.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "Siemens names SOA service bindings as a documented Teamcenter integration and customization surface.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.extensibility.scripting[2]",
   "note": "Siemens states that Active Workspace can be configured and extended, and that more capabilities ship only on Active Workspace each release.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-active-workspace-strategy/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.extensibility.scripting[3]",
   "note": "Siemens lists BMIDE with server-side and client-side development in the customization and extension documentation.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.data_access.export[0]",
   "note": "The official Teamcenter Connector is documented to access product data from Teamcenter.",
   "source": "https://docs.mendix.com/appstore/industry/teamcenter-connector/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.data_access.import[0]",
   "note": "The same Siemens Mendix documentation states that developers can create and modify product data in Teamcenter.",
   "source": "https://docs.mendix.com/appstore/industry/teamcenter-connector/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://plm.sw.siemens.com/llms.txt returned 404 on 2026-09-09, not an agent-documentation file.",
   "source": "https://plm.sw.siemens.com/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "verdict.scores.api",
   "note": "Official ITK and SOA APIs plus a Siemens Mendix connector support production integration, but public HTML omits auth, endpoints, and schemas, which keeps the path in the useful-but-limited band.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "verdict.scores.integrations",
   "note": "Bounded 2026-09-09 checks of Zapier, Make, Microsoft Power Automate (connector-reference index has no Teamcenter entry), and n8n found no Teamcenter connector, so the tracked iPaaS path is absent.",
   "source": "https://learn.microsoft.com/en-us/connectors/connector-reference/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-09",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as Siemens' current Teamcenter product page, including on-premises, customer cloud, and Teamcenter X SaaS delivery.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as Siemens' current public pointer to Teamcenter 2606 documentation, including ITK and SOA API references.",
   "source": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as Siemens Industry Software's current Teamcenter Connector for Mendix page.",
   "source": "https://docs.mendix.com/appstore/industry/teamcenter-connector/",
   "tier": "declared"
  },
  {
   "date": "2026-09-09",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as Siemens' current Teamcenter X SaaS page for this same PLM identity.",
   "source": "https://plm.sw.siemens.com/en-US/teamcenter/teamcenter-x-cloud-plm/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-09",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://plm.sw.siemens.com/en-US/teamcenter/"
   },
   {
    "type": "docs",
    "url": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/"
   },
   {
    "type": "sdk",
    "url": "https://docs.mendix.com/appstore/industry/teamcenter-connector/"
   },
   {
    "type": "docs",
    "url": "https://plm.sw.siemens.com/en-US/teamcenter/teamcenter-x-cloud-plm/"
   }
  ]
 },
 "homepage": "https://plm.sw.siemens.com/en-US/teamcenter/",
 "id": "siemens-teamcenter",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [],
   "coverage": "partial",
   "docs": "https://blogs.sw.siemens.com/teamcenter/teamcenter-documentation-home/",
   "exists": true,
   "kinds": [
    "soa"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "product-data"
   ],
   "import": [
    "product-data"
   ]
  },
  "extensibility": {
   "scripting": [
    "itk",
    "soa",
    "active-workspace",
    "bmide"
   ],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": false,
   "n8n": false,
   "power_automate": false,
   "zapier": false
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [
    {
     "maintained": true,
     "registries": [],
     "repo": "https://github.com/goenninger-b-t/tc-mcp"
    }
   ],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Siemens names Active Workspace as the HTML5 browser client and the path forward for Teamcenter, including cloud and Teamcenter X. Official ITK and SOA bindings, plus the Mendix Teamcenter Connector, are the documented machine surfaces. Visual control of Active Workspace or the Rich Client was not measured.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": true,
   "languages": [
    "java"
   ],
   "official": true
  }
 },
 "name": "Siemens Teamcenter",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "siemens-nx",
   "ptc-creo"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Siemens",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 5,
   "cli": null,
   "computer_use": null,
   "integrations": 0,
   "mcp": null,
   "overall": 5,
   "rpa": null
  },
  "summary": "The best evidenced path into Siemens Teamcenter is the vendor-declared SOA and Integration Toolkit (ITK) surface, not a public self-serve REST catalog. A Siemens Teamcenter documentation blog for the 2606 release states that Teamcenter documentation includes full API references for ITK and SOA service bindings, plus Active Workspace and BMIDE customization. Mendix documentation published by Siemens Industry Software describes Teamcenter Connector for Mendix, which reads, creates, and modifies Teamcenter product data against Teamcenter 2406+ and Teamcenter X 2506+. Active Workspace is the HTML5 browser client Siemens names as the path forward, including for cloud deployments. Teamcenter X is SaaS delivery of this same PLM identity, operated by Siemens; it is not a second product. Public HTML does not publish authentication methods, a current endpoint list, or unauthenticated SOA schemas; those references sit in Support Center documentation. Teamcenter Product Cost Management is outside this record. Siemens NX / Designcenter is a separate CAD identity. A third-party GitHub MCP server exists; Siemens has not declared a first-party MCP for Teamcenter. Zapier, Make, Microsoft Power Automate, and n8n had no Teamcenter connector on 2026-09-09. Computer-use viability is unassessed.\n"
 }
}