Threads on every entity.
Comment on a requirement, a BOM line, a baseline. Mentions, attachments, and resolution states. The discussion stays attached to the engineering artifact forever.
Tolerance stack-up shows ±0.15 mm at worst case. Is the assembly clearance still safe?
Re-ran the analysis. Updated SR-128 verification. See attached.
Approved for freeze. Adding to baseline v1.2.
Design reviews with structure.
Formal review workflows: define the scope, invite reviewers, capture decisions, lock the outcome under a baseline. Replaces the email-and-Excel checklist nightmare.
Pick the entities under review
Assign roles and approval rules
Threaded, resolved, captured
Signed, baselined, immutable
| Item | Qty | Editor |
|---|---|---|
| LiFePO4 Battery | 1 | AC editing |
| Motor Controller PCB | 1 | MD editing |
| BLDC Motor 750W | 4 | - |
| IMU Sensor | 2 | PS editing |
Real-time co-editing.
Multiple engineers in the same metamodel, the same BOM, the same requirements list. Cursor positions, live edits, presence indicators. Conflict-free, audited.
Every change. Every decision. Forever.
Audit trail is not an afterthought. It's the substrate. Who changed what, when, why, and which baseline locked it. Exportable as PDF for ISO 13485 and AS9100 audits.
| 14:32 | alice.chen@ | edited | SR-128 · Acceptance criteria | |
| 14:28 | marc.dubois@ | approved | Baseline v1.2 | |
| 14:21 | priya.shah@ | locked | BOM Drone Frame v3.0 | |
| 14:15 | ci-bot@ | linked | Test TC-501 → SR-128 |
Documents linked to the truth.
Specs, datasheets, PDFs, and CAD files, attached to the right entity. When the requirement changes, the documents that reference it are flagged automatically.
Battery datasheet rev B.pdf
→ Component · LiFePO4 Battery
DHF section 4 - Risk.docx
→ Risk item RI-014
Test report TC-501.pdf
→ Requirement SR-128
DO-178C SwReq baseline.xlsx
→ Baseline v1.2