element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Shift it! Warehouse Automation Design Challenge
  • Challenges & Projects
  • Design Challenges
  • Shift it! Warehouse Automation Design Challenge
  • More
  • Cancel
Shift it! Warehouse Automation Design Challenge
Forum Warehouse 13: The DataBase the heart of Warehouse 13
  • News
  • Forum
  • Projects
  • Leaderboard
  • Files
  • Members
  • Mentions
  • More
  • Cancel
  • New
Join Shift it! Warehouse Automation Design Challenge to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 0 replies
  • Subscribers 43 subscribers
  • Views 287 views
  • Users 0 members are here
  • flight simulator
  • nexgen
  • Database Design
  • Wharehouse 13
  • wharehouse Challege
  • Stack it
  • mysql
  • shift it
  • and Count
Related

Warehouse 13: The DataBase the heart of Warehouse 13

phoenixcomm
phoenixcomm over 1 year ago

image As the title says my MySQL Data Base is the heart of the Warehouse system.  Everything is just fluff, that helps the user(s). As this is a new system I don't have any web interface at this point, but I have the engine, more or less, well defined. So far I have described 4 tables, Categories, Manufactures, Info, History, and Spots. I will describe each of the tables.

  • Categories has four(4) columns: 
    CatID bigint(20) NO PRI NULL
    CatName varchar(100) NO NULL
    CatSeq bigint(20) YES NULL
    Note varchar(500) YES
  • Manufacturers has Six (6) columns: 

ManID bigint(20) NO PRI NULL auto_increment
ManName varchar(100) NO NULL
DivOf bigint(20) YES NULL
Alive enum('NULL','YES','NO','BOUGHT') YES NULL
Logo varchar(200) YES NULL
PhoneNumber varchar(20) YES NULL
Cage varchar(6) YES NULL
  • Info has thirteen(13) columns:  
InfoID bigint(20) PRI auto_increment
CatID bigint(20)
CatSeq bigint(20)
ManID bigint(20)
PartNumber varchar(50)
Description varchar200)
AltNumber varchar(100)
DateInfo timestamp current_timestamp()
DateInfo varchar(15)
BarCode varchar(15)
Photo varchar(1000)
WaitWeeks int(11)
Note varchar(1000)
  • Spots
SIDpot bigint(10) NO PRI NULL auto_increment
Location enum('Garage','Office','HallCloset') NO NULL
ShelfID int(11) NO NULL
BlueBin enum('O1','O2','O3','O4','O5','O6') NO NULL
SubSpot varchar(6) NO NULL

The first Table is the Categories. Ok, this may seem daunting but I will help you out. It's not really that bad. First, you have to understand what a Category is, it is just a numerical representation of its name.  A CatID and a parts CatSeq give you a unique number that can be used to reference the part.  There are 129 unique Categories, and more will be added as needed.

Next is the Manufacturers table again we just assign a unique number to each manufacturer. this is done with a feature of MySQL which is auto_increment. Again DB likes numbers. 

The next table is the heart of the thing it's called Info, again, the InfoID is an auto_increment. this is one of the main Keys.  You will notice the CatSeq number currently this number is incremented by hand. But what should happen is that it is left blank and the system finds the Categories.CatSeq increments it and writes it in the record that was just stored. There is also a field labeled NSN which stands for National Stock Number. This would correspond to the CAGE Code field which stands for Commercial and Government Entity which the DLA (Defense Logistics Agency) assigns. My  CAGE Code is 56L74. 

You also have a History table which is more or less the inventory it also has a unique number HistoryID which includes things like the purchase number, invoice number, and other information about the item. But it does not tell you where the thing is and that is done in the next table Spots.  

The Spots table tells you where the thing is. It has an enum which is the Location field, then SelfID, BlueBin SubSpot. For instance, let's say it's downstairs in the Garage. Its UniitID is C (third shelf on the left from the front), ShelfID is 2 which is the third shelf from the floor, 

Spot is B (second from the right, and its SubSpot is 2 which is the third box from the bottom of the shelf. So its ID is Garage-C2B2.

Ok, so now you know roughly what my DB structure is. The only other tables that I could/will add are InvoiceHeader, InvoiceDetail, PurchaceOrder, and PurchaceOrderDetail. I know you will ask questions so please do ~Cris H. 

  • Sign in to reply
  • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube