Skip to main content

System Hierarchy

Video transcript

00:00 — The System Hierarchy

The System Hierarchy. Your product as a tree, and a workbench per node.

00:08 — Build your product as a hierarchy

Every artifact in Creopus — requirements, FMEAs, DVPs, BOMs — attaches to a node in your product hierarchy. The hierarchy follows a 5-level V-Model — system → work-package → subsystem → assembly → subassembly — but you only have to use the levels you need.

00:32 — Fastest start — AI Generate

Paste a one-line product description ("Lithium-ion BMS for 400V automotive pack, ASIL-D"). The AI bootstraps a complete hierarchy with starter V-Model properties and requirements you can refine.

00:44 — Or build manually

Start with a top-level system node and add children as your understanding of the product grows.

00:53 — Your hierarchy lives here

Click any node to inspect or edit it. Right-click for the context menu (add child, rename, manage team, manage artifacts, delete). Hover over icons to preview traceability health for the subtree.

01:14 — A workbench per node

Once a node is selected, 15+ panels open up — V-Model properties, derived Requirements, Team (permissions inherit down the tree), attached Artifacts, Verification (the VCRM coverage matrix) and Validation, Config Status, PPAP, Branches, Blockers, TPMs, Gate Reviews, Baselines, Attachments, and History. System roots add Feed, Interfaces, System Model, and Trace Findings (traceability health for the whole tree).

01:51 — docs.creopus.ai

Full documentation, including every tool, is at docs.creopus.ai

The recursive V-model system-of-record everything else hangs on.

System Hierarchy

What it's for​

The backbone. A recursive V-model tree (System → Work Package → Sub-system → Assembly → Sub-assembly) that holds every node, artifact and team. Each node carries a status, a life-cycle gate plan, and thirteen tabs spanning the full V — requirements, verification & validation, configuration status, PPAP, TPMs, gate reviews and baselines. Bootstrap it with AI, cascade requirements across it, and watch the derivation graph keep the whole thing honest.

When to use it​

First thing on any project — everything else lives inside it.

How it works​

  1. Pick a system from the dropdown, or start one — New System, or AI Generate from a description. → AI Generate drafts the recursive V-model tree; each node auto-generates a unique Requirement Prefix (ECU, BMS…) and starts in Draft status.
  2. Set a life-cycle gate plan for the system, then Set plan. → Pick a preset — Commercial hardware, Aerospace/defense (NASA-derived reviews), NASA full life cycle (Pre-A…F, KDP), or AIAG APQP (PPAP-gated) — to enable ordered stage-gates across the whole system.
  3. Build the tree — each node has Add child, Edit, Manage team, Manage artifacts, Delete; search / expand / collapse the tree. → You compose the five levels by hand; Manage artifacts links a node’s deliverables, Manage team scopes access.
  4. Run Cascade Requirements from the toolbar. → A long-lived backend job fills every node level-by-level (parent context flowing to children) with Pause / Resume / Cancel / Reattach controls — close the browser and reattach later.
  5. Open a node and work its tabs — thirteen of them. → V-Model (lifecycle phases + inputs-from-above), Requirements (owned + inherited), Team, Artifacts (the work surface — staleness badges + “Derive from…” cards), Verification, Validation, Config Status, PPAP, Branches, Blockers, TPMs, Gate Reviews, and Baselines.
  6. Open the Derivation Graph from the toolbar. → The fresh / stale / gap map of every artifact across the tree — regenerate stale children in place or acknowledge the change.
  7. Invite teammates from a node’s Team tab; Clone or Export the system from the toolbar. → Access inherits down the subtree; Clone duplicates a whole system as a starting point, Export dumps the full structure.

Mechanics​

  • Recursive five-level V-model tree · per-node status
  • Life-cycle gate plans: Commercial / Aerospace-NASA / NASA KDP / AIAG APQP
  • 13 node tabs — V-Model · Requirements · Team · Artifacts · Verification · Validation · Config Status · PPAP · Branches · Blockers · TPMs · Gate Reviews · Baselines
  • Cascade Requirements — pausable, reattachable backend job
  • Derivation Graph: fresh / stale / gap coverage
  • Team access with ancestor inheritance
  • AI Generate · Clone System · Export System

Open System Hierarchy in the app