Clever functionality allows the system to extract all relevant component information from the MRP/ERP system (or other databases) without the need for direct connectivity. The process automatically populates and optimizes the internal database (CIS) as well as the embedded Manufacturers Alias Database within seconds.

At the heart of BOMArchitect is the CIS (Component Information Source), representing the key component information from your MRP/ERP system. The CIS information is automatically synchronized with the designated MRP/ERP system at any time.

The CIS architecture is highly optimised for use by our part search engine.

Customer-generated BOMs often have issues, such as incomplete or cryptic information, rudimentary part descriptions, not entirely correct manufacturer part numbers or old part manufacturer names, to name but a few. Mapping BOM parts with the internal part numbers in the ERP system is a lot of manual (often repetitive) work, which is difficult to automate. BOMArchitect offers two key solutions to this problem.

1 - BOMArchitect auto-learns component information relationships.

Once a BOM has been processed, the associations between the customer part information and the internal part information are recorded in an Approved Manufacturers List (AML) for future reference. This capability allows for maximum automation and results in an incredible efficiency boost in BOM processing.

2 - The "Manufacturer Alias Database" learns part manufacturer names and aliases.

Unfortunately, there is no standardisation of the manufacturer names used in BOMs. Consequently, part manufacturers have dozens of different name variants (aliases) in the field and this variation makes automation very difficult. The Manufacturers Alias Database in BOMArchitect solves this problem.

Customers supply part information in their BOMs in infinite variations. EMS providers are therefore forced to meticulously check and convert the incoming BOM content to comply with their internal identification conventions and to link it to Internal Part Numbers (IPNs). In many cases, part code numbers, manufacturer identifiers or descriptions in incoming BOMs are in an inconsistent format or even wrong; the cause of so many BOM errors.

Not only are the selections that a customer can make from the globally available part codes endless, but supply chain partners (customers, service providers and part vendors) often allocate their own part numbers, manufacturer identifiers and descriptions when recording information about components in their respective business systems.

EMS providers must link the incoming BOM content with their Internal Part Numbers (IPNs). This conversion (the "IPN mapping") must be performed before a reliable quotation can be generated or before a new product introduction (NPI) can take place.

The "Approved Manufacturers List" or "AML" in BOMArchitect solves this mapping problem.

Unfortunately, many OEMs do not accurately monitor their revisions, or do not use revision control at all. Failure to do so can result in catastrophic manufacturing issues, the worst possible outcomes being
products already having been built, which must be modified manually at great expense (which also affects product quality) or products that cannot be used at all.

These are good reasons for EMS providers to have internal systems which enable them to cross-check customer information, keep track of modifications (see also BOM compare) and to ensure that the information is complete and accurate prior to quoting. A system should also be in place to register undocumented last-minute modifications which customers may request by phone or email.
BOMArchitect has an extensive BOM revision control system, eliminating the risk of BOM revision confusions. Not only for BOMs but also for part code conversion lists sent by the customer (the formal AMLs).

All EMS providers know that finding all revised data in a BOM is critical and accuracy and completeness are essential. Although spreadsheets are used as the principal means for communicating the product materials within the electronics supply chain, a spreadsheet program is not a particularly efficient way of comparing bills of materials. It's simply that these programs (e.g. Excel, Calc) are so widely used.

BOM Compare in BOMArchitect is just a matter of clicking the reference BOM of any revision level.
The differences are then immediately shown. What has been added, what has been deleted and what has been changed. A filter function can selectively show the different modifications.
BOM Compare works not only in the customer BOM section, but also in the AML and the ERP sections of the BOM. So even fully processed BOMs of different revision levels can be compared.

Two key questions after receiving an RFQ are whether the product material costs are at the required price point and whether the parts are available to meet the supply deadline.

Since 2017, EMS providers have been facing challenging times with successive waves of supply shortages, price hikes and lengthening lead times. A critical shortage of parts and materials provoke both materials buffering and price increases. This will continue until demand stabilizes and part manufacturing capacity is in balance with demand.

One approach for you as an EMS provider is to ask your customers to always suggest alternative components (alternates) in their BOMs and/or in the Approved Manufacturers List (AML) or part code conversion list if they send one. Another approach is to propose alternates and ask your customer to review your proposal.

Either way, BOMArchitect offers extensive functionality for handling alternates.

After processing, the BOM contains a wealth of information which selectively can be used for viewing or for export to other business systems.

BOMArchitect supports the definition of user definable "Views". This, in combination with special filter settings, allows for an exact definition of the visible BOM information, to show exactly what is needed for a particular operation, department, function or customer. The views can be exported in different formats and configurations.

The position of every data column in the export can be defined centrally, as well as the public or private setting. This means that a BOM export to third parties using the "External" export function can never contain confidential information by mistake.

Export BOM to CAM, BOM to ERP, BOM to ...... Typing errors are a thing of the past!

By defining exactly the required import format for your CAM, ERP or other business systems, BOM content can automatically be transferred and automation can be brought to a higher level.

The export function to a spreadsheet (.xls) or delimited text (.txt) in different configurations exactly reproduces the view and filter settings in the active BOM View.

Additional settings allow seamless uploads to any ERP system, including XLM for deep integrations.

Export for the BOMArchitect Viewer

By exporting the processed BOM as a .cxb or a .cxbs (encrypted) file, the processed BOM information set will be available to be used in the free BOMArchitect viewer. The encrypted .cxbs file can be sent securely to customers by email.