It’s one of those interesting things that reminds you that the system is written by coders, who number lines of code by 10’s in case they have to squeeze something in there later. For operations (on jobs) it can be necessary if you have to add things in between. For materials, maybe not so much, but they kept the convention.
also, if the numbers in the engineering workbench won’t line up with the numbers on a job. Materials usually do (depending on the circumstance), but assembly sequences can’t with more than one level. So I wouldn’t get too hung up on making them match.
I’m an EE, so not much programming classes in my background. Only 3 classes in college. Pascal, 6502 Assembly (as part of microprocessor fundamentals class), and C(I took as an elective)
Bonus points if anyone knows what the acronym BUFFALO stands for.
OK… back on topic… Yes, the operations and materials in a BOM are auto sequenced by 10… this does have some benefits of allowing easy insertion of operations/materials. Once inserted they can be resequenced to get the spacing again if you like… (although do NOT do this if there is a product configurator attached to the BOM).
In reality, the sequence numbers values are not important. They are used, but can change when you “get details” into a job or quote.
yea… the following command would ALWAYS tell you exactly what is about to happen
50 IF A$="YES" THEN GOSUB 850
Those of us that had to learn programming back in the line numbered days, and when variables were only one digit long were some hard-core programmers. (For those novices out there… the $ at the end of “A$” told you that this was a string variable as opposed to a decimal variable “A”)