VR-COV-VR-BOM-ORCHID
① SA Source
- Source: 開啟完整 SA 文章
- Section:
VR NVL72 TCO: BoM and Power Budget Analysis - Line hint:
927
Context Before
VR NVL72 TCO: BoM and Power Budget Analysis
The VR NVL72 Component BoM and Power Budget Model ↗ provides a detailed analysis on the BoM and the Power Budget of the rack system.
Evidence
Context After
Source: VR NVL72 Component BoM and Power Budget Model ↗
The VR NVL72 is more expensive on a per-GPU capital cost basis, ~45% higher vs GB300s and ~14-15% higher vs the MI4XX given a higher server cost on a per GPU basis. This results in a higher Capital Cost of Ownership (TCO). For example VR NVL 72 Hyperscaler Arista has a capital cost of 2.86 per hour per GPU over a 4 year useful life. Our TCO Model runs on a 4y useful life for the purpose of calculating capital cost per hour to reflect a conservative business case, but most Neoclouds and Hyperscalers will use a 5-6y depreciation period and we think it is best to look at EBIT margins using this depreciation period. Our preferred yardstick is Project IRR, which is agnostic to the chosen depreciation period.
② Atomic Claim
The visible VR NVL72 BOM quantity column lists 72 Orchid boards per rack.
- Epistemic Mode:
ATTRIBUTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "ORCHID_BOARDS_PER_RACK",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"72"
],
"value_text": "72"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | VR NVL72 | 04_knowledge_base/VR NVL72 |
⑤ V2 Draft(需要修正時直接編輯)
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR,再手動執行 Repair Preview。
執行腳本前,Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
The visible VR NVL72 BOM quantity column lists 72 Orchid boards per rack.
V2 Semantic Frame Draft
{
"attribute": "ORCHID_BOARDS_PER_RACK",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/VR NVL72",
"label": "VR NVL72"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"72"
],
"value_text": "72"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ATTRIBUTED",
"mapping_status": "COMPLETE"
}⑥ Human Review
請在 Properties 逐項確認:
- 原文 → Atomic Claim 是否忠實
- Atomic Claim → Semantic Frame 是否忠實
- Canonical Entity mapping 是否正確
- Epistemic mode 是否保留原文語氣
- 最後選擇
review_action
Review state
Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。
