| ADR (Architecture Decision Record) |
A formal document that captures an important architecture decision, including the context, decision rationale, consequences, and alternatives considered. ADRs support a sign-off workflow and revision chain |
| Approval Status |
The review state of a card: Draft, Approved, Broken, or Rejected. Approved cards change to Broken when edited |
| Bookmark / Saved View |
A saved filter, column, and sort configuration in the Inventory that can be reloaded with one click |
| BPM |
Business Process Management — the discipline of modeling, analyzing, and improving business processes |
| BPM Row Order |
The display order of process type rows (Core, Support, Management) in the BPM process navigator, configurable by dragging rows |
| BPMN |
Business Process Model and Notation — the standard notation for modeling business processes (version 2.0) |
| Business Capability |
What an organization can do, regardless of how it does it |
| Calculation |
An admin-defined formula that automatically computes a field value when a card is saved |
| Card |
The basic unit of information in Turbo EA representing any architecture component |
| Card Type |
The category a card belongs to (e.g., Application, Business Process, Organization) |
| Confidence Score |
A 0–100% rating indicating how reliable an AI-generated description is |
| Data Quality |
A 0–100% completeness score based on filled fields and their configured weights |
| Diagram |
A visual architecture diagram created with the embedded DrawIO editor |
| File Attachment |
A binary file (PDF, DOCX, XLSX, images, up to 10 MB) uploaded directly to a card via the Resources tab |
| Fiscal Year |
The 12-month period used for budgeting and financial reporting. Configurable via Admin > Settings — the start month (January through December) determines how PPM budget lines are grouped |
| DrawIO |
The embedded open-source diagramming tool used for visual architecture diagrams |
| Cost Line |
A budget or actual cost entry (CapEx/OpEx) in a PPM initiative, used to track financial spending |
| Enterprise Architecture (EA) |
The discipline that organizes and documents an organization's business and technology structure |
| EOL (End of Life) |
The date when a technology product loses vendor support. Tracked via integration with endoflife.date |
| Gantt Chart |
A visual timeline with horizontal bars showing project schedule, duration, and progress for each work package and task |
| Initiative |
A project or program involving changes to the architecture |
| Lifecycle |
The five phases a component goes through: Plan, Phase In, Active, Phase Out, End of Life |
| LLM |
Large Language Model — an AI model that generates text (e.g., Ollama, OpenAI, Anthropic Claude, Google Gemini) |
| MCP |
Model Context Protocol — an open standard that lets AI tools (Claude, Copilot, Cursor) connect to external data sources. Turbo EA's built-in MCP server provides read-only access to EA data with per-user RBAC |
| Metamodel |
The data-driven model that defines the platform's structure: card types, fields, relations, and roles |
| Milestone |
A significant event or completion point in a project timeline, shown as a diamond indicator in the Gantt chart |
| Notification |
An in-app or email alert triggered by system events (todo assigned, card updated, comment added, etc.) |
| OData Feed |
A JSON data feed available on saved inventory views (bookmarks) for consumption by external tools such as Power BI or Excel |
| Ollama |
An open-source tool for running LLMs locally on your own hardware |
| Portfolio |
A collection of applications or technologies managed as a group |
| PPM |
Project Portfolio Management — the discipline of managing a portfolio of projects and initiatives with budgets, risks, tasks, and status reporting |
| Reference Number |
An auto-generated sequential identifier for ADRs (e.g., ADR-001, ADR-002) that provides a unique, human-readable label |
| Relation |
A connection between two cards that describes how they relate (e.g., "uses", "depends on", "runs on") |
| Resources Tab |
A card detail tab that consolidates Architecture Decision Records, file attachments, and document links in one place |
| RAG Status |
Red-Amber-Green health indicator used in PPM status reports for schedule, cost, and scope (mapped to Off Track, At Risk, On Track) |
| Risk Score |
An auto-calculated value (probability x impact) that quantifies the severity of a project risk in the PPM risk register |
| Saved Report |
A persisted report configuration with filters, axes, and visualization settings that can be reloaded |
| Revision (ADR) |
A new version of a signed ADR that inherits the content and card links from the previous version, with an incremented revision number |
| Section |
A groupable area of the card detail page containing related fields, configurable per card type |
| Signatory |
A user designated to review and sign off on an ADR or SoAW document. The signing workflow tracks pending and completed signatures |
| SoAW |
Statement of Architecture Work — a formal TOGAF document defining scope and deliverables for an initiative |
| SSO |
Single Sign-On — login using corporate credentials via an identity provider (Microsoft, Google, Okta, OIDC) |
| Subtype |
A secondary classification within a card type (e.g., Application has subtypes: Business Application, Microservice, AI Agent, Deployment). Each subtype acts as a sub-template that can control field visibility |
| Subtype Template |
The configuration of which fields are visible or hidden for a specific subtype. Admins configure this in the metamodel admin by clicking on a subtype chip |
| Stakeholder |
A person with a specific role on a card (e.g., Application Owner, Technical Owner) |
| Survey |
A data-maintenance questionnaire targeting specific card types to collect information from stakeholders |
| Tag / Tag Group |
A classification label organized into groups with single-select or multi-select modes, optional type restrictions, and an optional mandatory flag that blocks approval and feeds the data-quality score |
| Mandatory Tag Group |
A tag group flagged as required. Applicable cards cannot be approved until at least one tag from the group is attached, and satisfying it contributes to the card's data-quality score |
| EU AI Act Semantic Detection |
A TurboLens compliance pass that asks the LLM to flag cards embedding AI / ML capabilities (LLMs, recommendation engines, computer vision, scoring, chatbots, …) even when they are not explicitly classified as AI Agent / AI Model. Such findings are marked AI-detected |
| Initial vs Residual Risk |
Two assessments captured on every risk in the Risk Register. Initial is the unmitigated probability × impact; Residual is the post-mitigation probability × impact, editable once a mitigation plan exists. Both derive a level via the 4×4 matrix |
| Risk Reference |
A monotonic human-readable identifier (R-000123) assigned on risk creation. It stays visible in promoted-finding buttons (Open risk R-000123) and in the owner's linked Todo description |
| TOGAF |
The Open Group Architecture Framework — a widely used EA methodology. Turbo EA's SoAW feature aligns with TOGAF |
| Status Report |
A monthly PPM report tracking project health via RAG indicators for schedule, cost, and scope, along with accomplishments and next steps |
| Web Portal |
A public, read-only view of selected cards accessible without authentication via a unique URL |
| Work Breakdown Structure (WBS) |
A hierarchical decomposition of project scope into work packages, each with start/end dates and completion tracking. Used in the PPM Gantt chart |
| Work Package |
A logical grouping of tasks within a Gantt timeline that has its own start date, end date, and completion percentage |
| AI Suggestion |
An auto-generated card description produced by combining web search results with a Large Language Model (LLM) |
| AI Verdict |
A user's confirmation or rejection of the LLM's AI-bearing classification for a card (hasAiFeatures = true / false). Persists across re-scans so LLM drift cannot silently change the EU AI Act scope |
| GRC |
Governance, Risk and Compliance — the unified workspace at /grc with three tabs (Governance, Risk, Compliance) consolidating EA Principles, ADRs, the Risk Register and the Security & Compliance scanner |
| Phase G |
TOGAF ADM "Implementation Governance" phase. The source of the Risk Register's vocabulary and lifecycle |
| Risk Register |
Landscape-level register of architecture risks aligned to TOGAF Phase G. Lives at /grc?tab=risk. Distinct from the initiative-scoped risks captured inside PPM |
| Risk Owner |
The user accountable for a risk. Assignment auto-creates a system Todo on the owner's Todos page and fires a risk_assigned notification |
| Mitigation Task |
An owned work item attached to a Risk that captures concrete mitigation activity. Can be one-shot or recurring (daily / weekly / monthly / yearly). Recurring tasks roll forward calendar-correctly on completion |
| Mitigation Task Occurrence |
One scheduled instance of a Mitigation Task. Moves through scheduled → open → done / skipped. Snapshots the assignee at open and the owner-at-completion at close so audit answers survive owner rotation |
| Lead Time (Mitigation Task) |
Days before due_date a scheduled cycle is promoted to open and lands on the assignee's Todos. Smart per-unit defaults (1 / 2 / 7 / 14 for daily / weekly / monthly / yearly) capped at half the cycle |
| Compliance Finding |
A row in the Compliance register against a regulation × article. Authored manually by a reviewer or produced by a TurboLens AI scan; both kinds share the same lifecycle and can be promoted to a Risk |
| Macro Capability |
Level-0 grouping above L1 in the Capability Catalogue. Lands as a BusinessCapability card with attributes.capabilityLevel = "Macro" and a catalogueId prefixed MC-. Relaxes the hierarchy depth limit to 6 |
| Layered Dependency View (LDV) |
Turbo EA's house notation for dependency diagrams: cards grouped into the four EA layers as swim lanes, coloured by card type, with proposed cards rendered as dashed-border nodes with a green "NEW" badge. Used by the Dependencies Report, the Card Detail dependency section, and the TurboLens Architect target architecture |
| TIME (Tolerate / Invest / Migrate / Eliminate) |
A four-way portfolio classification framework for applications, popularised by Gartner. Each application is tagged with one disposition — Tolerate (keep as-is), Invest (fund improvements), Migrate (replace or rehost), or Eliminate (decommission). In Turbo EA it's commonly added as a single_select field on the Application card type and used as the colour axis of the Portfolio Report |
| Application Portfolio Rationalisation |
The most common first EA initiative on Turbo EA: inventory the applications in scope, classify each by business value and technical fitness, and assign a TIME disposition driving consolidate / replace / retire decisions |
| Crawl-Walk-Run |
The phased rollout pattern recommended in the EA Beginner's Guide. Crawl = narrow scope, Applications only, five fields per card. Walk = add capability mapping and a first portfolio analysis. Run = expand to processes, interfaces, data, and the advanced modules |