Difference between revisions of "Parts"
From apertus wiki
| Line 9: | Line 9: | ||
* fool proof and easy to read (not contain both O-letters and 0-zero numbers that are hard to differentiate - same with 1,7, l, I, etc.) | * fool proof and easy to read (not contain both O-letters and 0-zero numbers that are hard to differentiate - same with 1,7, l, I, etc.) | ||
* time saving to work with (codes shouldn't be too long) | * time saving to work with (codes shouldn't be too long) | ||
* all parts identification codes should be the same or very similar length | |||
Revision as of 20:21, 29 May 2018
1 Scope
Create a system that allows identifying each part in any AXIOM device with a unique identification code for assembly drawings/instructions, inventory keeping, spare part ordering/sales, billing of custom orders.
The system should be:
- human friendly (readable)
- machine friendly (possibility to draw the code in a barcode/QR code)
- flexible in the sense that it can be extended in the future with new categories/parts that are not yet known
- fool proof and easy to read (not contain both O-letters and 0-zero numbers that are hard to differentiate - same with 1,7, l, I, etc.)
- time saving to work with (codes shouldn't be too long)
- all parts identification codes should be the same or very similar length
1.1 AXIOM Beta
- 02-00: PCB Assemblies
- 02-01: Enclosures and Associated Mechanical Parts
- 02-02: Screws, Rods, Spacers, Rings & Nuts
- 02-03: Wiring & Connectors
- 02-04: Packaging
- 02-05: Tools & Test Components
- 02-06: Misc Materials
1.1.1 Notes & Thoughts
- A good way to illustrate a part naming scheme is like this:
- Shall we use 00, 10, 20, 30, 40 as second part numbering scheme so we can between any category add more (sub) categories: 21, 31, etc....?