Verwaltung von
Einzelteilen
Datenblaettern
Bausaetzen
Benutzertypen
Verbraucher
Administrator
Use-cases
Verwaltete Objekte
Einzelteile
Bausaetze
Anzahl baubarer Saetze bestimmen
Baussaetze reservieren / reservierungen aufheben
Bausaetze/Listen von Bausaetzen („heute bauen wir 10x X und 20x Y, sind Teile da?“)
| Field | Type | Comment |
| id | unique, pk, auto increment | |
| name | | |
| description | | |
| image | | opt |
| datasheet | | |
| watermarkhigh | | if below, order if ordering anyway |
| watermarklow | | if below, order required |
| stock | | how much is currently in stock |
| Field | Type | Comment |
| id | unique, pk, auto increment | |
| name | | |
| website | | |
| customerid | | our customer id for ordering |
| Field | Type | Comment |
| id | unique, pk, auto increment | |
| name | | |
| description | | |
link parts together to an assembly
does not allow for 'assemblies of assemblies' / baugruppen, would need one more layer ob abstraction
| Field | Type | Comment |
| assemblyid | fk | |
| partid | fk | |
| numrequired | | number of 'partid' required to build on 'assemblyid' |
| Field | Type | Comment |
| partid | fk | |
| vendorid | fk | |
| quantity | | minimum/recommended order quantity |
| price | | |
how to track parts and assembly pre-allocations / reservations in a way that allows you to keep allocations separate and allow to cancel individuall allocations in a clean way.
now to store datasheets? blobs?
do we have to associate / track similar parts by different manufactureres? („part X is out, but use Y instead“); possibly too complicated and overengineered
how to track part prices for resale? by part? fixed multiplicator?
project/microcontrollerforum/verwaltungssoftware.txt · Zuletzt geändert: 2010/06/27 12:30 von hadez
