Hi, we are like Mike. v61. We mainly use projects to group together
PO, jobs, Sales orders and invoices.
This has been discussed before and I think I would right in staying
that if you use the module like epicor intended then it is a great
tool. However, if you use it like we do then it helps greatly with
reporting. We use alot of inhouse corvu reports to generate the
required information. This is because we not a purely manufacturing
organisation.
There are example spreadsheet in mfgsys/ud/test which load directly
from vantage via the project build tables. These must tables must be
manually updated through the build routine. Also the example
spreadsheet are hooked up to the demo database so these would need
repointing.
There is a seperate option for the MS project build in project
maintenance screen. I can't remember whether this requires the build
analysis to be done or not. The ms build process generates a csv
file which can be imported into ms project. I think some mapping
needs to be completed on the first run. Sorry I am bit vague but I
don't use this option. But it can produce gannt charts etc. It is
possible to upload from ms project but I would advise against that.
It have found the build process a bit flaky but this is probably me,
again I don't use this.
You can have project phases which can be attached to jobs. You can
attach tasks to phases or just projects. Which could track
activities.
Milestones are related to billing, which can automatically generate
an invoice based on a fixed date , completion of job or a cost. The
only problem I found, from perspective, is that this will dump the
invoice value to company default deferred revenue and not the
related product group. This may not be a problem for you.
Budgets, They are just a simple budget for the whole project. Again,
we don't use these.
When Attaching PO which is not going straight to WIP then this
doesn't go into the project costs directly. The project module is a
manufacturing tool. However, you can report on this seperately.
You can attach individual jobs to different phases.
You can use projects in different entry screens. Such as in job
entry if you choose a project it show all the jobs in one go.
Simarily in the scheduling board.
Probably, it just like any other module you need to 'play' with it
and see what it can't do. We use it at the moment as a grouping tool
which allows us to create the various reports which need.
I hope this helps.
In version 8 there is much to the project module.
--- In vantage@yahoogroups.com, "brychanwilliams" <brychanw@...>
wrote:
PO, jobs, Sales orders and invoices.
This has been discussed before and I think I would right in staying
that if you use the module like epicor intended then it is a great
tool. However, if you use it like we do then it helps greatly with
reporting. We use alot of inhouse corvu reports to generate the
required information. This is because we not a purely manufacturing
organisation.
There are example spreadsheet in mfgsys/ud/test which load directly
from vantage via the project build tables. These must tables must be
manually updated through the build routine. Also the example
spreadsheet are hooked up to the demo database so these would need
repointing.
There is a seperate option for the MS project build in project
maintenance screen. I can't remember whether this requires the build
analysis to be done or not. The ms build process generates a csv
file which can be imported into ms project. I think some mapping
needs to be completed on the first run. Sorry I am bit vague but I
don't use this option. But it can produce gannt charts etc. It is
possible to upload from ms project but I would advise against that.
It have found the build process a bit flaky but this is probably me,
again I don't use this.
You can have project phases which can be attached to jobs. You can
attach tasks to phases or just projects. Which could track
activities.
Milestones are related to billing, which can automatically generate
an invoice based on a fixed date , completion of job or a cost. The
only problem I found, from perspective, is that this will dump the
invoice value to company default deferred revenue and not the
related product group. This may not be a problem for you.
Budgets, They are just a simple budget for the whole project. Again,
we don't use these.
When Attaching PO which is not going straight to WIP then this
doesn't go into the project costs directly. The project module is a
manufacturing tool. However, you can report on this seperately.
You can attach individual jobs to different phases.
You can use projects in different entry screens. Such as in job
entry if you choose a project it show all the jobs in one go.
Simarily in the scheduling board.
Probably, it just like any other module you need to 'play' with it
and see what it can't do. We use it at the moment as a grouping tool
which allows us to create the various reports which need.
I hope this helps.
In version 8 there is much to the project module.
--- In vantage@yahoogroups.com, "brychanwilliams" <brychanw@...>
wrote:
>this.
> Hi, What version of Vantage are you Running?
>
> --- In vantage@yahoogroups.com, "Jennifer" <jmesiano@> wrote:
> >
> > Are there any users out there running the Vantage Project
> feature?
> > How compatible is it with Microsoft Project? What are the
> pro's/con's
> > in using Vantage's version? Limitations? Our Engineering
> department
> > is looking at various options to handle our product planning
> projects.
> >
> > I haven't been able to find any literature or training on
> Any
> > help would be greatly appreciated.
> >
> > Jennifer Mesiano
> > Production Control
> > DuPAGE Machine Products
> > (630) 681-3547 (direct)
> >
>