What is the difference between the Design BOM template and an as-built BOM?

The Design BOM template captures intended product structure: product, assemblies, components, and explicit requirement or test references. It is not an as-built manufacturing record for one serial number or lot.

Do I need RTMify Live to use the template?

No. The workbook is a usable spreadsheet on its own. RTMify Live adds grouped XLSX ingest, continuous Design BOM sync, gap detection, impact analysis, BOM reports, and MCP querying.

What standards does the template target?

The page maps the template to BOM and design-output expectations commonly encountered in AS9100, ISO 13485, DO-178C, IEC 62304, ISO 26262, and ASPICE workflows.

Free Design BOM Template

Your BOM is already a spreadsheet.
Give it a schema.

The RTMify Design BOM Template gives product structure a consistent shape: one Product tab, one Design BOM tab, and direct columns for requirement and test references. Use it as a standalone workbook, export it as CSV, or connect it to RTMify Live for grouped workbook ingest, BOM gaps, impact analysis, and MCP queries.

Download Design BOM Template (.xlsx) Connect It To Live

What’s inside

README

Column reference, ingest paths, lifecycle/status notes, and standards mapping.

Product

`assembly`, `revision`, `full_identifier`, `description`, `Product Status`, `RTMify Status`.

Design BOM

Hierarchy, quantity, supplier/category, plus `requirement_ids` and `test_ids` for typed graph links.

The problem this solves

The BOM lives in Excel

Most teams still manage design intent in spreadsheets or delayed PLM exports. The data exists, but the structure is inconsistent.

Auditors ask product questions

“Which products use this part?” and “What requirement does this assembly satisfy?” are graph questions, not flat-sheet questions.

Trace links need a home

Requirement IDs and test IDs on BOM rows are explicit evidence. The template gives those references stable columns instead of burying them in comments.

What this template is

It is an opinionated Design BOM workbook. The Product tab anchors the graph. The Design BOM tab carries hierarchy, quantities, part revisions, and direct requirement/test references. The same column names work for spreadsheet sync, grouped XLSX ingest, CSV export, and BOM API payloads.

Standalone spreadsheet

Document products with lifecycle state on the Product tab.
Capture design-intent hierarchy on the Design BOM tab.
Export a single BOM group as CSV when you need a one-shot hardware BOM submission.

Connected to RTMify Live

Upload the workbook directly through POST /api/v1/bom/xlsx.
Attach it as a read-only Design BOM Sync source from the dashboard.
Query Components, Coverage, Part Usage, BOM Gaps, Impact, and a Design BOM report from the live graph.

Standards coverage

This is not a standards parser. It is a structured engineering artifact that supports the product-structure and design-output evidence expected in common regulated workflows.

Standard	Relevant clause	Why the template helps
AS9100	8.3.4 Design and development controls	Product and assembly structure can be tied directly to requirements, tests, and released revisions.
ISO 13485	7.3.4 Design and development review / outputs	Product-level anchor plus component-level trace inputs support device design-output evidence.
DO-178C	5.1.1 planning and configuration context	The workbook gives hardware assemblies and configuration items a stable identifier surface that can link into requirements and tests.
IEC 62304	5.3 software architectural design	The same product scaffold can hold embedded hardware/software product structure alongside the RTM workbook.
ISO 26262	Part 5 product development at hardware level	BOM items can carry exact requirement and test references rather than generic comments.
ASPICE	SYS.3 system architectural design	Product, assembly, and component relationships become queryable, reviewable design artifacts instead of static exports.

How it connects

1. Spreadsheet

Product rows establish the anchor. Design BOM rows establish the hierarchy and carry optional requirement/test IDs.

2. Live graph

Live ingests grouped workbook rows into DesignBOM and BOMItem nodes.

3. Traceability queries

Requirements, tests, test groups, code evidence, and serial-number evidence stay on the same graph, so BOM coverage and where-used answers are one traversal.

Use it standalone or with Live

Standalone

Download the workbook, fill in Product and Design BOM rows, and use it as your controlled design-output spreadsheet.

If you later need one-shot ingest, export one BOM group as CSV or upload the whole workbook as XLSX.

With RTMify Live

Connect the workbook as a secondary Design BOM Sync source or upload it through the dashboard. Live adds:

Components and Coverage views
Part Usage, BOM Gaps, and Impact analysis
Design BOM markdown reports
MCP tools and resources for BOM-centered questions

Download the workbook. No gate.

The template is free. RTMify Live is what turns it into a continuously queryable product-structure graph.

Download Design BOM Template (.xlsx) See Live Pricing

The RTMify product ladder

RTMify Template You are here

Build your RTM in a spreadsheet. Free download, no account.

RTMify Trace Available now

Generate a complete traceability artifact from your spreadsheet. Local, offline, no account.

RTMify Live Available now

Maintain traceability continuously. Live sync to your Google Sheet.

Your BOM is already a spreadsheet. Give it a schema.