This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi all,
We have a concept that we employ here where we hold a contest for people who report work orders as they're walking around (e.g. noticed paint chipped, a light bulb out, etc.).
The idea is that the person who reports the most in a month wins a prize. It helps to get people to notice minor things on such a big campus and ensures there is a steady backlog of work to be performed.
Previously, the way this was being tracked in Maximo has been completely wrong. It was tracked as a work type (even though it had nothing to do with the type of work). As a result, the two lenses couldn't be independent of one another.
After reviewing the concept, to designate a work order in this way, it's really a type of work order (not a type of work). It's not a priority code, and it doesn't seem to fit into any standard Maximo field. It has to do with how the work order is submitted, but not anything to do with the actual work itself.
So my questions are:
* Is there a standard Maximo field that can address this that could be displayed on the work order as a YORN? I'd like to appropriate a normal Maximo field if there is a Maximo concept that can be used in this way.
* Would it be wise in this case to create a custom field to store this information and track it?
Thanks, and have a good weekend!
--
Sean
I would go with a ... How Discovered field, with choice list.
�� Operator rounds
�� Maint staff walk-around
�� Engineering plant system walkdown
�� PM discovery
�� CM discovery
Sent on the Sprint� Now Network from my BlackBerry�
-----Original Message-----
From: "Killeen, Sean J." <sean.killeen@jhuapl.edu>
Sender: MAXIMO@yahoogroups.com
Date: Fri, 5 Oct 2012 12:50:30
To: MAXIMO@yahoogroups.com<MAXIMO@yahoogroups.com>
Reply-To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Best place for work order information pertaining to how it came in?
Hi all,
We have a concept that we employ here where we hold a contest for people who report work orders as they're walking around (e.g. noticed paint chipped, a light bulb out, etc.).
The idea is that the person who reports the most in a month wins a prize. It helps to get people to notice minor things on such a big campus and ensures there is a steady backlog of work to be performed.
Previously, the way this was being tracked in Maximo has been completely wrong. It was tracked as a work type (even though it had nothing to do with the type of work). As a result, the two lenses couldn't be independent of one another.
After reviewing the concept, to designate a work order in this way, it's really a type of work order (not a type of work). It's not a priority code, and it doesn't seem to fit into any standard Maximo field. It has to do with how the work order is submitted, but not anything to do with the actual work itself.
So my questions are:
* Is there a standard Maximo field that can address this that could be displayed on the work order as a YORN? I'd like to appropriate a normal Maximo field if there is a Maximo concept that can be used in this way.
* Would it be wise in this case to create a custom field to store this information and track it?
Thanks, and have a good weekend!
--
Sean
You could create another field and place near reported by and have a domain for customer call in, technician call in..etc.
This would also build a monthly metric for client vs technician
Shannon Sutton
Cell: (318) 334-8002
On Oct 5, 2012, at 12:50 PM, "Killeen, Sean J." <sean.killeen@jhuapl.edu> wrote:
> Hi all,
>
> We have a concept that we employ here where we hold a contest for people who report work orders as they're walking around (e.g. noticed paint chipped, a light bulb out, etc.).
> The idea is that the person who reports the most in a month wins a prize. It helps to get people to notice minor things on such a big campus and ensures there is a steady backlog of work to be performed.
>
> Previously, the way this was being tracked in Maximo has been completely wrong. It was tracked as a work type (even though it had nothing to do with the type of work). As a result, the two lenses couldn't be independent of one another.
>
> After reviewing the concept, to designate a work order in this way, it's really a type of work order (not a type of work). It's not a priority code, and it doesn't seem to fit into any standard Maximo field. It has to do with how the work order is submitted, but not anything to do with the actual work itself.
>
> So my questions are:
>
> * Is there a standard Maximo field that can address this that could be displayed on the work order as a YORN? I'd like to appropriate a normal Maximo field if there is a Maximo concept that can be used in this way.
>
> * Would it be wise in this case to create a custom field to store this information and track it?
>
> Thanks, and have a good weekend!
>
> --
> Sean
>
>
>
>
In TSRM area, you can find Source field under Ticket table with associated
with a domain called "Source" This field will show us How Ticket was
created ... like E-mail, Walk-In, Even Management, Phone Call etc.., This
fielld is cross referenced in SR, Incident, Problem areas
Similarly, you can create a field with you choice of values.
Vasu
On Fri, Oct 5, 2012 at 11:50 AM, Killeen, Sean J.
<sean.killeen@jhuapl.edu>wrote:
> **
>
>
> Hi all,
>
> We have a concept that we employ here where we hold a contest for people
> who report work orders as they're walking around (e.g. noticed paint
> chipped, a light bulb out, etc.).
> The idea is that the person who reports the most in a month wins a prize.
> It helps to get people to notice minor things on such a big campus and
> ensures there is a steady backlog of work to be performed.
>
> Previously, the way this was being tracked in Maximo has been completely
> wrong. It was tracked as a work type (even though it had nothing to do with
> the type of work). As a result, the two lenses couldn't be independent of
> one another.
>
> After reviewing the concept, to designate a work order in this way, it's
> really a type of work order (not a type of work). It's not a priority code,
> and it doesn't seem to fit into any standard Maximo field. It has to do
> with how the work order is submitted, but not anything to do with the
> actual work itself.
>
> So my questions are:
>
> * Is there a standard Maximo field that can address this that could be
> displayed on the work order as a YORN? I'd like to appropriate a normal
> Maximo field if there is a Maximo concept that can be used in this way.
>
> * Would it be wise in this case to create a custom field to store this
> information and track it?
>
> Thanks, and have a good weekend!
>
> --
> Sean
>
>
>
>
>
--
Thanks,
Vasu