{
 "categories": [
  "engineering",
  "enterprise",
  "document-control"
 ],
 "deployment": "hybrid",
 "evidence": [
  {
   "date": "2026-09-12",
   "fact": "homepage",
   "note": "IBM presents Engineering Requirements Management with DOORS Next as a scalable web-based requirements product and lists classic DOORS as a separate option on the same page.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "vendor",
   "note": "The opened product page is published by IBM and names IBM Engineering Requirements Management and DOORS Next.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "deployment",
   "note": "IBM describes DOORS Next as a scalable web-based requirements product for teams and suppliers across geographies.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "deployment",
   "note": "The 7.0.2 PDF documents a customer-hosted RM application with root services at https://host-name:9443/rm/rootservices. Combined with the web client, that is a hybrid identity.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "platforms",
   "note": "IBM describes DOORS Next as a web-based collaboration product. This record does not add desktop-client platforms without a current install matrix.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "license",
   "note": "The page is IBM's commercial Engineering Requirements Management offering. No public free tier is published on the opened page.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "status",
   "note": "IBM markets DOORS Next as the current web requirements product beside classic DOORS, with AI automations, configuration management, and compliance use cases.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.api.exists",
   "note": "The DOORS Next 7.0.2 documentation PDF includes 'Extending DOORS Next by using OSLC services' and states the RM application provides OSLC RM data sharing over REST architectural services.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.api.kinds[0]",
   "note": "Opened IBM's Jazz.net help topic. DOORS Next supports OSLC as an RM provider for RM V1 and V2 and consumes CM, QM, and RM V1/V2. Sharing uses HTTP linking, URI identification, and standard media types.",
   "source": "https://jazz.net/help-dev/clm/topic/com.ibm.rational.rrm.help.doc/topics/r_rm_oslc_services.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.api.kinds[1]",
   "note": "The current ELM API landing page lists DOORS Next Reportable REST API (v6.0 or higher, no significant changes for 7.x), Server API, Module API, ReqIF API, Readiness REST API, and in-server RM docs at /rm/doc/services.",
   "source": "https://jazz.net/wiki/bin/view/Deployment/ELMProductAPILanding",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.api.coverage",
   "note": "OSLC RM V2 provides service discovery, POST create, GET on requirements and collections, Resource Shape, and QUERY. Modules inside a collection are not available through GET. PUT of a module into a collection fails. Configuration-management operations are documented on a separate Oasis draft.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.api.docs",
   "note": "Opened the IBM Docs-hosted DOORS Next 7.0.2 PDF, including the OSLC provider operations table. Versioned IBM Docs HTML topics opened in this pass were JavaScript shells.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.mcp.first_party",
   "note": "Opened IBM's MCP catalog README. It does not name DOORS Next or Engineering Requirements Management. Catalog silence is not a vendor declaration of absence.",
   "source": "https://raw.githubusercontent.com/IBM/mcp/main/README.md",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.mcp.first_party",
   "note": "Official MCP registry search for doors returned unrelated outdoor and 'DoorsetBook' servers, not IBM DOORS Next. Registry silence is not proof that IBM ships no first-party server.",
   "source": "https://registry.modelcontextprotocol.io/v0.1/servers?search=doors",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.integrations.zapier",
   "note": "Zapier returned HTTP 404 for /apps/ibm-doors/integrations on 2026-09-12.",
   "source": "https://zapier.com/apps/ibm-doors/integrations",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.integrations.make",
   "note": "Make's app catalog rendered a coming-soon page for /ibm-doors-next on 2026-09-12.",
   "source": "https://apps.make.com/ibm-doors-next",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.integrations.power_automate",
   "note": "Microsoft Learn /connectors/ibmdoorsnext/ returned 404. The connector-reference index opened the same day had no DOORS Next entry.",
   "source": "https://learn.microsoft.com/en-us/connectors/ibmdoorsnext/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.integrations.n8n",
   "note": "n8n built-in app-node docs returned page-not-found for n8n-nodes-base.ibmdoorsnext on 2026-09-12.",
   "source": "https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.ibmdoorsnext/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "IBM documents OSLC RM provider operations, including programmatic factory creation of requirement resources.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "IBM documents ReqIF import and export for exchanging requirements and metadata with other RM tools, including classic DOORS.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.extensibility.scripting[2]",
   "note": "The ELM API landing page lists the DOORS Next Client Extension API and 7.0.3 extension examples as a JavaScript extension surface.",
   "source": "https://jazz.net/wiki/bin/view/Deployment/ELMProductAPILanding",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.data_access.export[0]",
   "note": "IBM documents exporting artifacts from a requirements project or component into ReqIF files.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.data_access.import[0]",
   "note": "IBM documents importing artifacts from ReqIF files into a requirements project or component.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://www.ibm.com/llms.txt returned HTTP 404.",
   "source": "https://www.ibm.com/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "The product /llms.txt URL returned an IBM products HTML index, not an llms.txt agent document.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "verdict.scores.api",
   "note": "OSLC RM V2 plus the ELM Reportable REST landing is a usable production path, but public HTML omits authentication, module coverage is incomplete, and current IBM Docs HTML topics did not render, which keeps the path in the useful-but-limited band.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "verdict.scores.integrations",
   "note": "Bounded 2026-09-12 checks of Zapier, Make, Microsoft connector slugs plus the connector-reference index, and n8n built-in nodes found no DOORS Next connector.",
   "source": "https://learn.microsoft.com/en-us/connectors/connector-reference/",
   "tier": "scraped"
  },
  {
   "date": "2026-09-12",
   "fact": "freshness.watch[0].url",
   "note": "Opened the current IBM Engineering Requirements Management product page, which keeps DOORS Next and classic DOORS as separate options.",
   "source": "https://www.ibm.com/products/requirements-management-doors-next",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "freshness.watch[1].url",
   "note": "Opened the current ELM API landing page that replaced the deprecated CLM landing page, including the DOORS Next API table.",
   "source": "https://jazz.net/wiki/bin/view/Deployment/ELMProductAPILanding",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "freshness.watch[2].url",
   "note": "Opened the current IBM Docs-hosted DOORS Next 7.0.2 PDF, including the OSLC provider chapter.",
   "source": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "freshness.watch[3].url",
   "note": "Opened the current Jazz.net help topic for extending DOORS Next with OSLC services.",
   "source": "https://jazz.net/help-dev/clm/topic/com.ibm.rational.rrm.help.doc/topics/r_rm_oslc_services.html",
   "tier": "declared"
  },
  {
   "date": "2026-09-12",
   "fact": "freshness.watch[4].url",
   "note": "Opened the current IBM/mcp catalog README. DOORS Next is not listed.",
   "source": "https://raw.githubusercontent.com/IBM/mcp/main/README.md",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-12",
  "volatility": "medium",
  "watch": [
   {
    "type": "product",
    "url": "https://www.ibm.com/products/requirements-management-doors-next"
   },
   {
    "type": "docs",
    "url": "https://jazz.net/wiki/bin/view/Deployment/ELMProductAPILanding"
   },
   {
    "type": "docs",
    "url": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf"
   },
   {
    "type": "docs",
    "url": "https://jazz.net/help-dev/clm/topic/com.ibm.rational.rrm.help.doc/topics/r_rm_oslc_services.html"
   },
   {
    "type": "docs",
    "url": "https://raw.githubusercontent.com/IBM/mcp/main/README.md"
   }
  ]
 },
 "homepage": "https://www.ibm.com/products/requirements-management-doors-next",
 "id": "ibm-doors-next",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [],
   "coverage": "partial",
   "docs": "https://www.ibm.com/docs/en/SSUVLZ_7.0.2/pdf/doorsnext_master_702.pdf",
   "exists": true,
   "kinds": [
    "oslc",
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "reqif"
   ],
   "import": [
    "reqif"
   ]
  },
  "extensibility": {
   "scripting": [
    "oslc",
    "reqif",
    "client-extension"
   ],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": false,
   "n8n": false,
   "power_automate": false,
   "zapier": false
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Documented automation is OSLC RM REST, the ELM Reportable REST landing, and ReqIF exchange. The DOORS Next browser UI remains unassessed. This is DOORS Next, not classic IBM Engineering Requirements Management DOORS (DOORS 9).\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "IBM Engineering Requirements Management DOORS Next",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "siemens-teamcenter",
   "ibm-maximo"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "IBM",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": 0,
   "mcp": null,
   "overall": 6,
   "rpa": null
  },
  "summary": "The best evidenced agent path into IBM Engineering Requirements Management DOORS Next is the OSLC Requirements Management REST surface, not classic DOORS 9, not Maximo, and not Teamcenter. IBM's DOORS Next 7.0.2 documentation PDF states that the RM application provides OSLC RM V1 and V2 as a service provider, including service discovery, POST for requirement creation, GET on requirements and collections, Resource Shape, and V2 QUERY on requirements, collections, and OSLC links. Configuration-management operations sit on a separate Oasis draft. Jazz.net's current ELM API landing page, build basis 7.0.x, additionally names the DOORS Next Reportable REST API for v6.0 and later, a Server API, Module API, ReqIF API, Readiness REST API, and in-server docs at /rm/doc/services. Public HTML opened in this pass does not publish the authentication contract. The Jazz native-client authentication wiki required a Jazz.net login, so auth methods stay unnamed. Reportable REST is documented on IBM Docs as a reporting and ETL read path; the IBM Docs HTML topics opened here were JavaScript documentation shells. IBM/mcp does not list a DOORS Next server. Named Zapier, Make, Power Automate, and n8n connectors were not present in the catalogs checked. Computer-use viability is unassessed.\n"
 }
}