Appearance
Bill of Materials (BOM)
What is the BOM Module?
The Bill of Materials module manages structured lists of components and materials required for projects, assemblies, or production. You can upload BOMs from Excel or CSV files, and the system validates each line item against your product catalog -- checking for duplicates, missing manufacturer part numbers (MPN), and component lifecycle status. Version control tracks every change with a full audit trail, so you always know who modified what and when. The module also provides cost estimation by pulling the latest supplier quotes and can convert BOM items directly into RFQs for competitive sourcing.
How It Connects
| Direction | Connected Module | Relationship |
|---|---|---|
| In <-- | Products | BOM line items reference products from the catalog |
| In <-- | Components | Electronics components provide lifecycle and compliance data for BOM items |
| Out --> | RFQs | BOM items can be converted to RFQ line items for sourcing |
| Out --> | Projects | BOMs are linked to projects for material planning and budget tracking |
| Both | Suppliers | Supplier quotes feed cost estimation; BOM-to-RFQ flows back to suppliers |
Step-by-Step Guide
- Create a new BOM -- navigate to Catalog > BOMs > New BOM. Enter the BOM name, project reference (optional), and description.
- Upload or add items -- choose one of two methods:
- Upload from file: Click "Import" and upload an Excel (.xlsx) or CSV file. Download the template first to ensure correct column mapping.
- Add manually: Click "Add Line Item" and search for products by IPN, MPN, or description.
- Map columns (upload only) -- the system displays a column mapping screen. Match your file's columns to Tawridy fields: MPN, description, quantity, reference designator, etc.
- Run validation -- click "Validate BOM". The system checks every line item for:
- Duplicate entries (same MPN appearing multiple times)
- Missing or unrecognized MPNs (not in catalog or component database)
- Lifecycle issues (NRND, EOL, or Obsolete components)
- Compliance flags (non-RoHS, REACH concerns)
- Review validation results -- the validation report categorizes issues by severity:
- Errors (red): Must be resolved before proceeding (e.g., missing MPN)
- Warnings (amber): Should be reviewed (e.g., EOL component with alternatives available)
- Info (blue): Informational only (e.g., duplicate consolidated)
- Resolve issues -- fix errors by mapping to existing catalog items, adding missing products, or selecting alternative components suggested by the system.
- Estimate costs -- click "Estimate Cost". The system pulls the latest pricing from supplier mappings and quotes to calculate per-item and total BOM cost.
- Convert to RFQ -- select items that need sourcing and click "Create RFQ". The system generates an RFQ pre-populated with the selected BOM items, quantities, and specifications.
- Version and lock -- once finalized, lock the BOM version. Future changes create a new version with change tracking.
BOM Validation Summary Example
| Check | Items Checked | Passed | Warnings | Errors |
|---|---|---|---|---|
| Duplicate MPNs | 156 | 148 | 8 (consolidated) | 0 |
| Catalog Match | 156 | 132 | 0 | 24 (unmapped) |
| Lifecycle Status | 132 | 118 | 10 (NRND) | 4 (Obsolete) |
| RoHS Compliance | 132 | 130 | 2 (unknown) | 0 |
| Total | 156 | -- | 20 | 28 |
Version History Example
| Version | Date | Changed By | Changes | Status |
|---|---|---|---|---|
| v1.0 | 2026-01-10 | Ahmed K. | Initial upload (156 items) | Superseded |
| v1.1 | 2026-01-15 | Sara M. | Replaced 4 obsolete components | Superseded |
| v2.0 | 2026-02-01 | Ahmed K. | Added 23 items for Phase 2 scope | Active |
Key Fields Explained
| Field | Description |
|---|---|
bom_name | Descriptive name for the BOM (e.g., "Fire Alarm System - Building A"). |
bom_number | Auto-generated reference (format: BOM-YYYY-NNNN). |
version | Current version number with major.minor format (e.g., v2.0). |
project | Linked project for budget and material tracking. |
line_items | List of items: MPN, IPN, description, quantity, reference designator, unit cost, line total. |
total_items | Count of unique line items in the BOM. |
total_cost | Sum of all line item costs based on latest supplier pricing. |
validation_status | Overall BOM health: Valid, Has Warnings, Has Errors. |
lifecycle_summary | Breakdown of component lifecycle statuses across all items. |
status | Draft, Validated, Active (locked), Superseded, or Archived. |
source_file | The original uploaded Excel/CSV file, retained for reference. |
change_log | Detailed record of every modification across all versions. |
Tips & Best Practices
TIP
Always download and use the Tawridy BOM template before uploading. The template includes all required columns and data format examples. Using a non-standard format results in mapping errors and failed validations.
WARNING
Never skip the validation step. Ordering against an unvalidated BOM risks procuring obsolete components, duplicating orders (if consolidated quantities are not reviewed), or missing items entirely. The validation report takes seconds and prevents costly mistakes.
TIP
Use the "Cost Comparison" feature to estimate BOM cost across different supplier combinations. The system can show the lowest-cost mix, the fastest-delivery mix, and the single-supplier consolidation price for each scenario.
TIP
When a BOM contains obsolete or EOL components, use the built-in cross-reference tool to find pin-compatible or form-fit-function alternatives before converting to RFQ. This saves back-and-forth with suppliers during the quoting process.
WARNING
Locking a BOM version prevents all edits. If changes are needed after locking, you must create a new version. Always communicate version changes to project stakeholders, as cost estimates and RFQs reference specific BOM versions.
FAQ
Q: What file formats are supported for BOM upload? A: Excel (.xlsx) and CSV (.csv). The system also accepts tab-separated values (.tsv). For best results, use the Tawridy BOM template available from the import screen.
Q: How does duplicate detection work? A: The system identifies duplicates by MPN. When duplicates are found, you can choose to consolidate (sum quantities) or keep them separate (useful when different reference designators require separate line items for tracking).
Q: Can I merge two BOMs? A: Yes. Open the target BOM and use "Merge BOM" to import line items from another BOM. The system checks for overlapping MPNs and lets you choose whether to sum quantities or skip duplicates.
Q: How is cost estimation calculated? A: For each line item, the system checks (in order): active supplier quotes, supplier catalog pricing from product mappings, and historical PO prices. The most recent and relevant price is used. Items without any pricing data are flagged as "unpriced".
Q: Can I export a BOM? A: Yes. Export options include Excel, CSV, and PDF. The PDF export includes a formatted table with cost summary, validation status, and lifecycle indicators -- suitable for sharing with project managers or clients.