Eugue,

I don't believe there are any limits. We have 742 pieces of equipment logged in our asset register.

We do manage our inventory with guru.

We do not use their purchasing module at the moment. All of our PO's are created manually.

The modules in guru each have a report editor built in if you want to create your own reports. The system does come with many predefined reports. I think we've only created 3 custom reports at the moment.

M

quote:

Originally posted by Eugene:
Does Guru
* Has limits on number of equipment can be registered?
* Do include spare parts management?
* Do you run the purchase requisitions in it?
* How about reporting options?

quote:

Originally posted by MKV:
Bryan,

Our maintenance department consist of 4 technicians and two engineers. We have guru installed on a file server with 7 users. No problems with performance. It's quite fast. I don't think I've heard anyone complain about it.

M

If only 7 users and 6 are from Maintenance, how the clients/equipment owners enter their maintenance requests/notifications?
Do they submit them in paper and someone enter all notifications at the system?

Eugene,
What is driving the change is a failed Maximo upgrade and the blame game as to who's at fault. Contract obligations were not met and now there is a want for more $$$ to make it right. They knew when they left from on-site applications that the software was not usable. If you read the Yahoo users group you see many problems and few solutions with the newer versions. It seems as if the repair is always in the next patch and you just have to sit and wait for it to happen.I just don't think we want to continue with the constant problems and it isn't the most user friendly software as well. Most of our techs cringe at using it as it is on the older version. More or less it's just time for a change.

Eugene,

When operators or other staff members have a request, they can submit them by either of the following means:

1. Come up to our service window and make a request. When this is done, one of our technicians creates the work request.

2. Call our services phone and make a request. One of the technicians records the information into a work request.

3. We have a work request application on a PC on the shop floor that operators can input a work request themselves.

It's worked out really well for us.

MIKE

quote:

Originally posted by Eugene:

quote:

Originally posted by MKV:
Bryan,

Our maintenance department consist of 4 technicians and two engineers. We have guru installed on a file server with 7 users. No problems with performance. It's quite fast. I don't think I've heard anyone complain about it.

M

If only 7 users and 6 are from Maintenance, how the clients/equipment owners enter their maintenance requests/notifications?
Do they submit them in paper and someone enter all notifications at the system?

Eugene, about your question of the labour costs, we solved it quite simple.

Every one in the company has job description that is rated in a category. There is a list where the minimum and maximum for each category defined, and also a "prefered optimum" for each category.
We took the prefered salary of each job description, took the employee number and we have "price / wrench time" of the job. These intern labour costs are for comparison, the material and service costs are more important, since Human Resources don't use this data for payment of employees.
I guess with the EAM stuff, you would have to report training, housekeeping , safety talks , job preparation, attending meetings also to see your money at the end of the month.

That takes out the discussion of letting a less experienced guy do the work, because it will look good (cheap) on paper.