Requirements - Bill of Material (BOM) Example
Blog: Biz-Performance, David Brown
Requirements - Bill of Material (BOM) Example
This is a typical example used to define the requirements for the Bill of Material (BOM) module within a Software Application.
1.1 | General requirements |
(a) | Assembly details may be maintained for finished goods and phantoms. |
(b) | Parts explosions may be up to xx levels. |
(c) | There will be an interface with the Purchase Ordering system to generate works orders for items which are to be re-ordered. |
(d) | An interface to the Sales Ordering system is also desirable for items which are to be assembled for customers. |
(e) | Assembly codes will be up to xx characters. |
(f) | A trial kitting facility is required. |
(g) | Product codes will be up to xx alphanumeric characters. |
(h) | Stock will be held in up to xx warehouses. |
(i) | The facility to track serially numbered items through the system is required. |
(j) | The option of updating physical stock levels on issue or completion of the works order should be available. |
(k) | The system should allow for the partial completion of works orders and provide a facility for scaling down items such as electricity and labour. |
(l) | If using LIFO or FIFO, issue of components to a works order should update the LIFO/FIFO batch/queue file, and add to the batch of finished goods. |
1.2 | Input |
(a) | The BOM system will interface with a inventory control system and automatically update physical and on-order stock levels. |
(b) | Inventory values should be updated with the rolled up code of the finished product. |
(c) | The total cost of the finished product (ie inclusive of labour, overheads, etc) will update the "current" cost value on the stock file. |
(d) | Physical and on-order fields will be updated on works order issue/completion. |
(e) | Input of a purchase order will automatically generate a works order for items assembled using the BOM system. |
(f) | The Sales Ordering system will automatic-ally generate a works order for items which are assembled using BOM. |
(g) | Transactions for all products in the BOM system will be recorded on the stock history file. |
(h) | The system should generate the works order number automatically. |
(i) | On issue of a works order, the system should prompt for serial numbers for any items which are flagged as serially numbered items in the products file. |
1.3 | Data stored |
(a) | For each assembly the following reference data is required: |
Header: | |
* assembly code; | |
* warehouse; | |
* short description; | |
* long description; | |
* special instructions; | |
* alpha code; | |
* phantom assembly. | |
Detail: | |
* warehouse; | |
* product code/material; | |
* short description; | |
* units; | |
* quantity; | |
* stage of production. | |
(b) | The facility to enter codes for items such as overheads, labour and machine wastage is required. |
(c) | For each work order the following data will be held: |
Header: | |
* work order number; | |
* date entered; | |
* date required; | |
* assembly number; | |
* instructions; | |
* trial (yes or no); | |
* quantity. | |
Detail: | |
* warehouse; | |
* product/service; | |
* unit; | |
* quantity; | |
* short description; | |
* long description. | |
(d) | The facility to amend individual items making up each assembly is required. |
(e) | Free format comment lines should be available on the works order. |
1.4 | Data outputs |
1.4.1 | Enquiries |
(a) | By work order number, the facility to enquire on the status of each works order is required. |
(b) | By assembly number, there should be a facility to display all works orders for individual assemblies. |
(c) | The ability to view all works orders containing specific products by product code is required. |
(d) | Access to valid serial numbers by product code should be available. |
1.4.2 | Reports |
(a) | An assembly file report showing details of all assemblies, component parts and number level of explosion for each sub-assembly. |
(b) | A trial kitting report showing shortages of components is mandatory. |
(c) | A report showing in which assemblies a particular component is used. |
(d) | A works order status report. |
(e) | A full history report recording transactions for all assemblies and products. |
(f) | A report showing the total cost (ie inclusive of labour, overheads, etc) of all assemblies. |