Sub-Assembly Travelers Not in Chronological Order

Kinetic ERP
1

We are starting to use sub-assemblies in our jobs. We’ve found, if we have Finished Good X set as sub-assembly 0, and manufactured component Y set as sub-assembly 1 everything looks good on the routing and works from a system standpoint. However, when printing the traveler it will start with material, then list sub-assembly 0, then go back to sub-assembly 1. This is not correct chronologically which causes a bit of unnecessary confusion, I’m curious if anyone else has encountered/addressed this issue?

Thanks!!

2

Not sure exactly what you’re seeing… but, for me:

I see Job Asm: 0

  • Subassembly Components (that fall inside Asm 0… assy 1 & 2)
  • Raw Material Components (that fall inside Asm 0)
  • Operations (that fall inside Asm 0)

Then I see Job Asm: 1

  • Subassembly Components (that fall inside Asm 1… assy 3, 4, 5, 6, 7, 8, etc.)
  • Raw Material Components (that fall inside Asm 1)
  • Operations (that fall inside Asm 1)

Then I see Job Asm: 3

  • No subassemblies here…
  • Raw Material Components (that fall inside Asm 3)
  • Operations (that fall inside Asm 3)

Then I see Job Asm: 4

  • No subassemblies here…
  • Raw Material Components (that fall inside Asm 4)
  • Operations (that fall inside Asm 4)

So… for me, the order is Assy 0, then 1 (the first child), then 3 (the first grandchild), then 4 (the second grandchild).

… this seems like the proper flow for me.

3

In building jobs, you have to view Assembly 0 as the assembly that goes into stock/ships to customer.
Note: Job Entry and Method tracker view is opposite to each other. (I have no clue why).
When adding a child assembly, it should be referenced as a material of assembly 0.

I hope this helps.

image
image1766×755 66.5 KB

1 Like
4

image
image1766×755 81.9 KB

1 Like
5

Thanks @LisaShirley , that is how we have it set up as well. But it seems rather counterintuitive when we’re printing our job travelers and the first page shows Assembly 0 starting at OP 120, then they need to flip back to halfway through the traveler to find OP 10.

I wasn’t sure if other companies have this problem and just deal with it or what? It wouldn’t be an issue if we were all digital, but we’re far from that in our current state.

6

Asm 0 will always print first.
If they want to print Asm 1 first, they can choose to print Asm 1 seperately and then go back and print Asm 0.

image
image835×638 17 KB

1 Like
7

Sorry, this is a long post… but I wanted to explain and help demonstrate how the Traveler is constructed:

This doesn’t sound right at all. Remember though that there would probably be an Op 10 on Assy 0, and an Op 10 on Assy 1, 2, 3, 4, etc.

Are you using a customized Traveler? If so, does the order of sorting change if you print the standard out-of-the-box version?

If you want to modify how things are sorted, you can do so in Report Builder. If you are using a customized traveler already, perhaps you should verify the settings in there and see if someone else inadvertently changed the sorting.

Below is how the traveler is set up (out of the box)…

Again, like I posted earlier, you should see Assy 0 first. It will list all the child subassemblies of Assy 0, all the raw materials of Assy 0, then all the operations of Assy 0.

Then, on a new page (if you selected that option when you printed), you’ll see Assy 1. It will list all the child subassemblies of Assy 1, all the raw materials assigned to Assy 1, then all the operations of Assy 1.

I will say it is confusing because the report doesn’t show what assembly the operations are for on any given page. You have to pay attention to where it announces it is now showing the details for the next assembly. Below is an example:

The first page of your traveler should include this:
image

This is the part I’m making as Assy 0.

If I scroll down to Page (5) of my traveler… I see operations 70, 80 & 85 on this particular job. Nowhere on this page does it say these operations are for Assy 0.
image

If I scroll down to page (14)… I see these… Again, I see operations 70 and 80. But these are for Assy 1.

image
image87×520 6.11 KB

If I scroll back to Page (9)… this really itty-bitty reference is the only thing that tells me I’m now looking at details for Assy 1, and the operations I was looking at on Page (14) are for Assy 1:
image

One page (19) I see I’m now starting details for Assy 3:
image

Its a smaller assembly, not as many operations, but these operations appear on Page (20)… they are for Assy 3:
image

Assy (4) starts on page 22
Assy (5) starts on page 24
Assy (6) starts on page 26
Assy (7) starts on page 28
Assy (8) starts on page 30

Then… Assy (2) starts on page 32

Assy (2) is the second Child of Assy 0. Below is my job structure… and you’ll see it lists the assemblies in the routing/traveler in the same order they appear below:

Assy 0, 1, 3 - 8, then 2
image

8

@dcamlin thank you very much for the detailed explanation. I should have realized this earlier but walking through your steps was a bit of a lightbulb moment for me.

We are using a customized traveler which I hadn’t even considered initially as it’s been in place long before I started and we never modify it. This is why I couldn’t filter as Lisa suggested above. I’m working with someone more knowledgeable on the subject to access Report Builder to see if we can change the order of assemblies that are displaying.

I didn’t mention that we build our routings out to still have sequential operations so there is no overlap. For example: Grandchild Asm 2 starts with OP 10, 20, 30. Child Asm 1 has OP 40, 50, 60. Parent Asm 0 has OP 70, 80, 90. Our goal is to get these to print out in the order they’re manufactured (Asm 2 > 1 > 0) which would start at OP 10 in this instance and finish at OP 90.

Thank you again!

1 Like
9

Okay… that makes a lot more sense :rofl:

Below are the “standard” settings (Group Sortings) in Report Builder:

The top group is the “job”… and the only sorting here is an expression to start each assembly on a new page (if you chose that option when you printed).

image
image975×157 20.4 KB

image
image833×89 31.5 KB

… so you can leave that one alone.

The Second group is sorted by your BOM Sequence:

image
image975×159 20.2 KB

image

… you may want to sort this Z to A, instead of A to Z

The third group is sorted by the AssemblySeq:

image
image975×155 20.7 KB

image

… you may want to sort this Z to A, instead of A to Z

The 4th group is sorted by Operation Sequence:

image
image975×156 20.6 KB

image

I would assume you’d leave this one A - Z

1 Like
10

Thanks again, this has been a huge help!!

1 Like