Subassemblies & Job Manger?

Thanks very much Norman.

Kind Regards,
Nancy

--- In vantage@yahoogroups.com, Norman Hutchins <nhutchins@...> wrote:
>
> Hello Nancy,
>
>
>
> We are/were looking at subassemblies for a number of reasons.
>
>
>
> 1. Fewer open jobs, fewer jobs to create.
>
> 2. Cost roll-up for progress billing
>
> 3. Visibility for Shop Floor, Accounting and Sales to track status of
> lower level jobs, from one place (Job Tracker).
>
>
>
> Though it appears there are some down sides that we were not aware of.
>
>
>
> 1. Subs do not show up in Job Manager or Time Phase, so there is no
> place to see all the demand you have for these parts.
>
> 2. Subs do not have transaction again them, there for things like Part
> Transaction History, and Part Advisor do not work either.
>
>
>
> We have not made a decision either way yet, we have a meeting today at 11 to
> talk about the pro's and con's. If we find any other information out I'll
> be sure to share it here.
>
>
>
> Norman
>
>
> [Non-text portions of this message have been removed]
>
Happy Monday Everyone!

We would like to switch to using subassemblies for most of our jobs.
However, I have one planner that is against it and I�m trying to solve this
issue.. Their concerns follow:

1) Lack of visibility on the line items in Job Manager � Parts that are
on sub-assemblies do not show up in Job Manager so it�s harder to track
where and when parts are being made or if they are being made unless you are
working in the top level job � you must know the job number to reference
this information



2) Once a part is made into a sub-assembly it is tied to the top job
regarding Released Status and Print status. I was of the understanding that
we were working to stop releasing jobs to the Production Manager unless ALL
the materials were available. Once you print ANY sub-assy on any job the job
must be �Released� in order to have materials issued to it as well as having
labor transactions done on it. This releases the whole job not just the
sub-assembly that we�re working on.



3) We currently track job status from our area by �release� status and
�print� status. I know of no other way to confirm that I job is with the
Production Manager.

It seems that once a part is set to a subassembly it no longer shows up in
Job Manger as demand, therefore making the planner lose visibility. When I
look at the help file for Job Manger it says;

�The Demand grid lists all the upcoming quantities that need to be filled
for the current part. Demand entries for a part can come from three sources
� sales order releases, job materials, and* job assemblies*.�

Which makes it sound like subassemblies should show up here (unless I�m
reading this wrong) but they don�t. They also don�t seem to show up on Time
Phase either.

Any thoughts, am I missing something?

Norman Hutchins

Network Administrator

Howell Laboratories, Inc.

Shively Labs

207-647-3327


[Non-text portions of this message have been removed]
We have one additional issue with Subassemblies - They do not show up on
the Part Advisor, or on the Part Transaction History tracker.

Therefore, we cannot see how many times we have made a part and the
actual vs estimated results.

Has anyone developed a tracker to show the subassemblies?

Metro Machine & Engineering
Let's see if we can't tackle this. It's a more common problem (and
decision) than you think.
1) Lack of visibility on the line items in Job Manager - Parts that
are on sub-assemblies do not show up in Job Manager so it's harder to
track where and when parts are being made or if they are being made
unless you are working in the top level job - you must know the job
number to reference this information.
You are correct that parts in subassemblies do not show up on
the job manager. Only the top level part shows because that is the part
that is being made. There is only one job being produced. The sub
assemblies are just that - sub parts in the main job. The job tracker
and Priority Dispatch report will show the status of the sub assemblies.
This method also reduces inventory transactions.

What I did for one customer was create a dashboard with all of
the open job assemblies.

One thing is that you basically schedule the entire job. You can
go into the scheduling board and move the subassemblies around if you
wish but the entire job is scheduled as one item. The dependencies of
the top level are scheduled to achieve the final assembly required date.

2) Once a part is made into a sub-assembly it is tied to the top
job regarding Released Status and Print status. I was of the
understanding that we were working to stop releasing jobs to the
Production Manager unless ALL the materials were available. Once you
print ANY sub-assy on any job the job must be "Released" in order to
have materials issued to it as well as having labor transactions done on
it. This releases the whole job not just the sub-assembly that we're
working on.
This is correct. You are releasing the entire job and not just a
part of it. What you can do is release the job but only print and send a
specific assembly to production. You could add a checkbox to the
assembly record to say that it was printed and show it on the dashboard
I described above.

3) We currently track job status from our area by "release" status
and "print" status. I know of no other way to confirm that I job is with
the Production Manager.
Again, you could add checkboxes to the assembly record that
would give that status. The check boxes would be for your use only and
the entire job would still need to be released, but you could control
the assembly records and what appears on the dashboard.

Remember that the job manager is exactly that, JOB manager. If
you make the entire part 'inline' you are making the final assembly and
all sub assemblies ("Pull as Assembly - TRUE") as one job. If you make
the parts 'off-line' as a material demand of the upper level part you
will require jobs for each part you make off-line ("Pull As Assembly -
False"). You can have subassemblies mixed with some as sub assembly and
some as materials, depending on how your shop flows.

Hope this helps.

Charlie Smith
Smith Business Services / 2W Technologies LLC
www.vistaconsultant.com <http://www.vistaconsultant.com/> /
www.2WTech.com
<<Picture (Device Independent Bitmap)>> <<Picture (Device
Independent Bitmap)>>



-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Norman Hutchins
Sent: Monday, April 05, 2010 2:48 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Subassemblies & Job Manger??

Happy Monday Everyone!

We would like to switch to using subassemblies for most of our jobs.
However, I have one planner that is against it and I'm trying to solve
this issue.. Their concerns follow:

1) Lack of visibility on the line items in Job Manager - Parts that
are on sub-assemblies do not show up in Job Manager so it's harder to
track where and when parts are being made or if they are being made
unless you are working in the top level job - you must know the job
number to reference this information.
2) Once a part is made into a sub-assembly it is tied to the top
job regarding Released Status and Print status. I was of the
understanding that we were working to stop releasing jobs to the
Production Manager unless ALL the materials were available. Once you
print ANY sub-assy on any job the job must be "Released" in order to
have materials issued to it as well as having labor transactions done on
it. This releases the whole job not just the sub-assembly that we're
working on.
3) We currently track job status from our area by "release" status
and "print" status. I know of no other way to confirm that I job is with
the Production Manager.

It seems that once a part is set to a subassembly it no longer shows up
in Job Manger as demand, therefore making the planner lose visibility.
When I look at the help file for Job Manger it says;

"The Demand grid lists all the upcoming quantities that need to be
filled for the current part. Demand entries for a part can come from
three sources - sales order releases, job materials, and* job
assemblies*."

Which makes it sound like subassemblies should show up here (unless I'm
reading this wrong) but they don't. They also don't seem to show up on
Time
Phase either.

Any thoughts, am I missing something?

Norman Hutchins

Network Administrator

Howell Laboratories, Inc.

Shively Labs

207-647-3327


[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links





[Non-text portions of this message have been removed]
Hi Norman,

We are implementing Epicor 9. We have wrestled with whether to use pull as assembly or not. I hope you don't mind my asking, but why do most of your people want to use pull as assembly?

Thanks,
Nancy Hoyt

--- In vantage@yahoogroups.com, Norman Hutchins <nhutchins@...> wrote:
>
> Happy Monday Everyone!
>
> We would like to switch to using subassemblies for most of our jobs.
> However, I have one planner that is against it and I'm trying to solve this
> issue.. Their concerns follow:
>
> 1) Lack of visibility on the line items in Job Manager – Parts that are
> on sub-assemblies do not show up in Job Manager so it's harder to track
> where and when parts are being made or if they are being made unless you are
> working in the top level job – you must know the job number to reference
> this information
>
>
>
> 2) Once a part is made into a sub-assembly it is tied to the top job
> regarding Released Status and Print status. I was of the understanding that
> we were working to stop releasing jobs to the Production Manager unless ALL
> the materials were available. Once you print ANY sub-assy on any job the job
> must be "Released" in order to have materials issued to it as well as having
> labor transactions done on it. This releases the whole job not just the
> sub-assembly that we're working on.
>
>
>
> 3) We currently track job status from our area by "release" status and
> "print" status. I know of no other way to confirm that I job is with the
> Production Manager.
>
> It seems that once a part is set to a subassembly it no longer shows up in
> Job Manger as demand, therefore making the planner lose visibility. When I
> look at the help file for Job Manger it says;
>
> "The Demand grid lists all the upcoming quantities that need to be filled
> for the current part. Demand entries for a part can come from three sources
> – sales order releases, job materials, and* job assemblies*."
>
> Which makes it sound like subassemblies should show up here (unless I'm
> reading this wrong) but they don't. They also don't seem to show up on Time
> Phase either.
>
> Any thoughts, am I missing something?
>
> Norman Hutchins
>
> Network Administrator
>
> Howell Laboratories, Inc.
>
> Shively Labs
>
> 207-647-3327
>
>
> [Non-text portions of this message have been removed]
>
Hello Nancy,



We are/were looking at subassemblies for a number of reasons.



1. Fewer open jobs, fewer jobs to create.

2. Cost roll-up for progress billing

3. Visibility for Shop Floor, Accounting and Sales to track status of
lower level jobs, from one place (Job Tracker).



Though it appears there are some down sides that we were not aware of.



1. Subs do not show up in Job Manager or Time Phase, so there is no
place to see all the demand you have for these parts.

2. Subs do not have transaction again them, there for things like Part
Transaction History, and Part Advisor do not work either.



We have not made a decision either way yet, we have a meeting today at 11 to
talk about the pro�s and con�s. If we find any other information out I�ll
be sure to share it here.



Norman


[Non-text portions of this message have been removed]