Forum Topic Postings

 

  Anonymous

 

 

The underlying database is based on a hierarchical tree based structure that has a finished product identifier (i.e. something the business most likely sells to others) as the topmost entry. At that topmost level the list of component product identifiers that are required for the manufacture of the finished item will comprise either raw material (items that by definition have no components i.e. lower level structure) or sub-assemblies (items that do identify a number of components required for their manufacture). Raw material product identifiers would presumably be sourced from the company supply chain or might even be free issue material from the customer. Sub-assembly product structure follows the same definition features outlined above for a finished product identifier and this hierarchical tree structure extends down further levels until all identifiable aspects of the overall build have been defined. The bottom level for any branch of the tree is identified by the fact that the component list comprises nothing but raw material product identifiers. There are no limits to the number of levels involved and the component requirement within the bill-of-material may be defined to 7 decimal places. The latter is further extended by the fact that requirement is identified in relation to an individual production batch quantity relating to each finished item or sub-assembly.

 

 

How does Orbitall handle multi-level, complex product structure definition; are there any relevant limits or restrictions?