Maximo

 View Only

  • 1.  Usability Pros and Cons for using Classifications on WOs

    Posted Sun July 17, 2022 07:24 AM
    Hello Everyone

    We are thinking to use Classifications on WOs, rather than adding fields on WO application for different departments

    Can you please share your thoughts and experiences on Pros and Cons? Especially, with respect to usability and searching and easiness?

    ------------------------------
    mx pro
    ON
    ------------------------------

    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Usability Pros and Cons for using Classifications on WOs

    Posted Mon July 25, 2022 01:59 AM

    My "2 cent" ….

    I'll look in to WORKTYPE. We have several different departments with their "own set of classes" - I have thought of WORKTYPE as a way to "bundle" different set of classes together and then I will have an easier way to search (and write the SQL). For some department we have implemented this, but it may not be as "fine-tuned" as you may want it to be.

    If you add attributes to the WORKORDER table – I believe you will get better performance when you search, compared to if you use classes at it may involve several tables.



    ------------------------------
    Niclas Havrup
    ------------------------------

    Original Message


  • 3.  RE: Usability Pros and Cons for using Classifications on WOs

    Posted Mon August 01, 2022 01:51 AM

    Tend to agree.

    We've found classifications great for searching for specific types of records, well beyond the typical high level groupings we have in the typical type fields.

    However when you use attributes on a classification instead of full time fields, it can be hard to search for those from an end user perspective (compared to a Type popup domain list), and you have to populate them in the Specs table (which again is not particularly user friendly).


    So as always it will depend on your specific use case, but the classification approach has not been as nice to use or layout as individual fields.



    ------------------------------
    Richard Jackson
    Asset Information and Systems Manager
    Massey University
    Palmerston North
    New Zealand
    ------------------------------

    Original Message


  • 4.  RE: Usability Pros and Cons for using Classifications on WOs

    IBM Champion
    Posted Tue August 02, 2022 09:50 AM
    Good evening Mx pro,

    I feel like I would need to get more questions answered as my consulting hat wants to be put on in order to provide you guidance if classifications are even something that should be considered over other fields that can make querying easier.

    I would start by asking what is different for each department that needs to be collected and how the data is to be used.  What you think is unique actually is not unique.

    Usually, classifications in the context of the work orders and SR's are asking questions to assist with collecting enough information in a formal structure that can assist the maintenance technician/planner/supervisor enough information to assess what the job is about in order to get it fixed as soon as possible   This is not department specific, instead, it is process specific.

    If you need to involve fields for assigning to a department then you have the owner group or work group fields.

    Yes, an attribute can be a question of asking a question of which department this should be directed towards.

    PROS
    -----------
    • Provides standardized description (if enabled)
    • Able to be changed at anytime

    CONS
    ----------
    • Not searchable on the list tab.  NB: This is only referring to the work order and not the location or asset.  NB: You can of course put it on the list tab.
    • You have to go to the Advanced Search to search by classification
    • Attribute search is not based on the classification

    As always, I'm happy to have a chat.

    ------------------------------
    ===============================
    Craig Kokay,
    Lead Senior Maximo/IoT Consultant
    ISW
    Sydney, NSW, Australia
    Ph: 0411-682-040
    =================================
    #IBMChampion2022
    ------------------------------

    Original Message


  • 5.  RE: Usability Pros and Cons for using Classifications on WOs

    IBM Champion
    Posted Tue August 02, 2022 03:40 AM
    A rhetorical question. Is there much point using a classification if you don't use the attributes in the Specification? I think generally not. Consider that configuration is relatively easy, and searching by classification is not, because you are searching by the CLASSSTRUCTUREID as the key to the classification. Therefore, my view is use classifications when you are going to use specifications.

    With regard to WO Classifications/Specifications you need then to ask - Where will I capture the data for the attributes in the specification? The most likely scenario is on the Service Request and using a set of aligned classifications on SR/WO is a great use of WO classifications. But if SRs are not being used this way, you need to answer that previous question - Who will enter the attributes of the WO Specification? Whatever the answer will surely give you the answer to whether it is a good idea to use WO Specifications (or not).

    There is never a one answer fits all to most functional questions. But when trying to think about solutions you do need to think more about how the Maximo system will be used by end-users, rather than just how do I configure the Maximo solution for end users. It is a different way of thinking.

    ------------------------------
    Andrew Jeffery
    Maximo SME
    ZNAPZ b.v
    Barnstaple
    0777 1847873
    ------------------------------

    Original Message