One cornerstone of JIT is that it's insane to make, store, and then retrieve subassemblies, because all the associated labor and space contributes nothing to the finished product. ... unless you are selling subassemblies.
DFMA does not require modularity; it only deals with the difficulty of assembly, for a module, or for an entire product, or for a particular JIT workstation's operations.
There are good reasons to make modules, but they don't all have to do with assembly sequence.
Example: I bought a replacement handle for my Ford van door. But dealers don't stock the handle. They stock a 'door kit', which includes every removable part for a given door. Which reduces the number of items a dealer has to handle and stock, and makes it unlikely that I'll walk away from the parts counter without handing the dealer $100 or more.
Similarly, for any product, you might want to group individual parts into kits for your service people or your dealers, reducing the number of Field Replaceable Units everyone has to document, handle, store, and deliver.
So a given product could have several BOMs, all structured differently, and several sets of MIs, depending on whether you are building final product or FRUs or something else.
Product engineers are not all-knowing about this stuff, though it is to their great benefit to understand it. Just don't assume that you know the best sequence of assembly, even if you designed the product; especially if you designed it.
Mike Halloran
Pembroke Pines, FL, USA