BOM generation is generally a module within CAD/EDA software. The BOM generator typically pulls information from the design files (eg. quantities, designators, component type, ...) and also has the ability to bring in information from an external database ( eg. suppliers, last price paid, ...)
The main value in a BOM generator is this ability to automatically collect information from the design files and, typically in-house, component databases, due to its integration. Any standalone web app would risk losing this valuable integration.
Note that the component databases are typically in-house, built up over the years, based on knowledge accumulated over many designs. Some engineers will even carry a personal database from job to job with them.
Rather than a BOM generator, I'd say a valuable product would be in a serious on-line database of electronic components. EDA manufacturers and component manufacturers have half baked efforts, but they all suffer from their being an attempt at customer lock-in rather than being a truly useful resource.
It'd be a huge job collating and maintaining such a database, but it could be quite lucrative, especially if it included a facility to link suppliers with customers. Think imdb, freedb or cddb, but for components instead of movies or songs. The entry for each component might include:
* Manufacturer's data
* Schematic symbols
* PCB footprints
* Parametric information
* A list of suppliers
* MOQ, lead time, price, ... for each supplier
* and so on...
You'd also need to be able to generate library data in various formats to suit each EDA/CAD tool, or provide an API through with EDA/CAD tools could issue queries on the fly.
It would also be a neat trick to integrate with some of the circuit layout website that are appearing, leaving open the possibility of building an EDA "design flow" by exchanging data between using a set of web sites.
The main value in a BOM generator is this ability to automatically collect information from the design files and, typically in-house, component databases, due to its integration. Any standalone web app would risk losing this valuable integration.
Note that the component databases are typically in-house, built up over the years, based on knowledge accumulated over many designs. Some engineers will even carry a personal database from job to job with them.
Rather than a BOM generator, I'd say a valuable product would be in a serious on-line database of electronic components. EDA manufacturers and component manufacturers have half baked efforts, but they all suffer from their being an attempt at customer lock-in rather than being a truly useful resource.
It'd be a huge job collating and maintaining such a database, but it could be quite lucrative, especially if it included a facility to link suppliers with customers. Think imdb, freedb or cddb, but for components instead of movies or songs. The entry for each component might include:
* Manufacturer's data
* Schematic symbols
* PCB footprints
* Parametric information
* A list of suppliers
* MOQ, lead time, price, ... for each supplier
* and so on...
You'd also need to be able to generate library data in various formats to suit each EDA/CAD tool, or provide an API through with EDA/CAD tools could issue queries on the fly.
It would also be a neat trick to integrate with some of the circuit layout website that are appearing, leaving open the possibility of building an EDA "design flow" by exchanging data between using a set of web sites.
--- CAD = Computer Aided Design
EDA = Electronic Design Automation