We are in the process of implimenting vantage and plan to use service
connect for labor entry. This is our plan: Our work sites are at
remote locations so our daily labor data will be collected in an
excel spreadsheet that we have developed that our supervisors will
fill out and e-mail in. This will contain such data as job#,
operation, employee code, employee name, hours worked, resource, and
resource hours. Our IT department is developing this using table
info that will be preloaded in the spreadsheet so that the supervisor
has alot of pre-filled boxes and some that autofill (ie.. if they
pick the employee name, it will autofill the employee number). The
first page of this spreadsheet will contain the header info and line
info to create a .csv file that will be dropped into vantage service
connect. From this point we are still conceptual. We are using open
4 payroll which will accept a .csv file for input so the spreadsheet
should load payroll info direct into Open4. we then plan to take
actual Labor hours and labor costs out of Open4 and load them into
vantage via labor adjustment. We are going to have the vantage
consultant write the service connect to do this. The final part of
this is to have the production and resource (burden) hours input
through labor entry (with zero labor hours and labor cost since this
will come through open4) via service connect. In testing this seams
to work inputing them this way through vantage and supposedly if we
can do it manually in vantage then we can replicate it to work
through service connect. We are doing it this way to obtain ACTUAL
labor cost right out of Open4 payroll in the job. If anyone has any
thoughts, comments, or question feel free to e-mail me direct
(ddibert@...).
connect for labor entry. This is our plan: Our work sites are at
remote locations so our daily labor data will be collected in an
excel spreadsheet that we have developed that our supervisors will
fill out and e-mail in. This will contain such data as job#,
operation, employee code, employee name, hours worked, resource, and
resource hours. Our IT department is developing this using table
info that will be preloaded in the spreadsheet so that the supervisor
has alot of pre-filled boxes and some that autofill (ie.. if they
pick the employee name, it will autofill the employee number). The
first page of this spreadsheet will contain the header info and line
info to create a .csv file that will be dropped into vantage service
connect. From this point we are still conceptual. We are using open
4 payroll which will accept a .csv file for input so the spreadsheet
should load payroll info direct into Open4. we then plan to take
actual Labor hours and labor costs out of Open4 and load them into
vantage via labor adjustment. We are going to have the vantage
consultant write the service connect to do this. The final part of
this is to have the production and resource (burden) hours input
through labor entry (with zero labor hours and labor cost since this
will come through open4) via service connect. In testing this seams
to work inputing them this way through vantage and supposedly if we
can do it manually in vantage then we can replicate it to work
through service connect. We are doing it this way to obtain ACTUAL
labor cost right out of Open4 payroll in the job. If anyone has any
thoughts, comments, or question feel free to e-mail me direct
(ddibert@...).
--- In vantage@yahoogroups.com, "Craig Weiss" <cweiss@...> wrote:
>
> I haven't done one for labor entry yet, but I have a workflow for
> budget entry that requires the same 2 step process.
> I do a get by id to see if the budget entry exists. If it doesn't,
then
> I add the header record and the detail, if it does, then I simply
add
> the detail. Every row of the input file has the header values, as
well
> as the detail values.
> It cycles through this process for every detail. It may not be the
most
> efficient coding, but it is effective.
> Our labor entry folks are pretty unhappy with the interface, so I
may
> try to write something in the near future, but I don't have
anything
> right now.
> My biggest issue with using service connect for this type of
solution
> is that I don't know of a good way to provide feedback to the user
on
> the success or failure. ESC is very sensitive to file formats, so
there
> needs to be a way to show the user that all of their updates failed
or
> succeeded. I just don't know how to effectively accomplish that yet.
> Craig
> --- In vantage@yahoogroups.com, "brucewbrannan" <bruce.brannan@>
> wrote:
> >
> > I'm interested in how this would work. Currently, through labor
> entry,
> > you have to first create the record for the overall hours for the
day
> > (shift) and then you have to add the detailed labor records
afterward.
> >
> > --- In vantage@yahoogroups.com, "rec0rder" <rec0rder@> wrote:
> > >
> > > Does anyone have any service connect templates for entering
labor
> > > hours into Vantage 8.03?
> > >
> >
>