Database Design

Years of Experience: 15

Database: Microsoft SQL Server

  • Databases Maintaining
    • Industrial: 9
    • Commercial: 1

Database Structure: Relational and Non-relational

Most programming required a strict relational design though some data was applied in as non-relational. In the designs of material management, there is one database where the material is strictly controlled. The strictly controlled material requires permissions to edit. The purpose for the strictly controlled material table was to keep preferential descriptions out of the material ordering process. The model number and the descriptions are held as closely to manufacturer (or supplier) information as possible to remove the possibility of unclear intent. Maintaining a clear and consistent intent in purchasing removes guesswork. In my disposition, if I maintain the strict intent, then if an error occurrs, the error can be more quickly resolved.

Ex. BOM Program: The information to the customer may not require specific detail and a general description can be used. However, if the Purchase Order goes to the manufacturer or the supplier, the document should be specific in intent.

Ex. Bids: Often a bid project does not require the exact instrument, but at least a model number loosely representing the item. The greater accuracy in the bid, the better the information flows through to engineering and purchasing. The bid material list is unique to the bid. The material information can be edited as needed and it will not affect the primary database.

Ex. BOM: Like Bids, the material records are completely editable. The information should be exactly what the project requires. However, if the BOM is to be presented to the customer, then too much detail will be counterproductive is working through the project scope. For example, if the material is a magnetic flowmeter flowtube, the model number should include the grounding rings. The description does not require a confirmation of grounding ring inclusion. The customer may just need to confirm the flowtube’s size.

Ex. Requisitions: This is a program where the BOM is transferred to. To transfer the BOM, all records need to exist in the primary database. At the BOM program is the best time to ensure model number and description is correct. Generally, a supplier/manufacture quote is available, and confirmation of the data is confirmed.

Rate: Please request a quote and provide a scope of work. Consulting is available.

Leave a Comment

Your email address will not be published. Required fields are marked *