Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Difference between location hierarchy vs. other hierarchies

    Posted Fri October 15, 2021 09:28 AM
    Edited by System Admin Wed March 22, 2023 11:45 AM
    MAM 7.6.1.2:

    I'm familiar with Maximo hierarchies like the following:
     - Classifications hierarchy (CLASSSTRUCTURE table)
     - Assets: The PARENT field in the ASSET table
     - Workorders: The PARENT field in the WORKORDER table

    Those hierarchies are relatively straightforward. Each child has a single parent. A parent can have multiple children.


    When it comes to the location hierarchy, it seems like that hierarchy is different than the others:
    - There can be multiple location hierarchies -- called systems.
    - A location can have multiple parents, if those parents are from different systems(?)
    - Locations in Maximo have a more complex table structure:
        - LOCATIONS (doesn't have a PARENT field, unlike other primary tables like CLASSSTRUCTURE, ASSET or WORKORDER)
        - LOCHIERARCHY (has a PARENT field)
        - LOCANCESTOR (similar to the ancestor table in other Maximo hierarchies, but unlike the others, it doesn't have a HIERARCHYLEVELS field)
        - Other?


    Am I on the right track? What are some notable differences between the location hierarchy vs. other Maximo hierarchies?

    Thanks.



    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: Difference between location hierarchy vs. other hierarchies

    Posted Mon October 18, 2021 03:58 AM
    Locations can belong to multiple location systems, they can have parents in each of those systems. Location Systems can be hierarchical, only one parent. Location Systems can also be network systems where a location can have multiple parents. Think of an high voltage electric tower, invariably it is supporting two electric circuits, one on the left and one on the right, the tower has two parents.

    Kind regards

    Andrew Jeffery
    Maximo SME
    +31 627 020 728
    andrew.jeffery@znapz.com


    Ceresstraat 1, 4811 CA Breda
    The Netherlands
    +31 76 790 11 88
    www.znapz.com







    This email is intended only for the use of the party to which it is addressed and may contain information that is privileged, confidential, or protected by law. If you are not the intended recipient you are hereby notified that any dissemination, copying, or distribution of this email or its contents is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer.







    Original Message


  • 3.  RE: Difference between location hierarchy vs. other hierarchies

    Posted Mon October 18, 2021 10:08 AM
    I tried using the NETWORK system which is supposed to allow you to have a LOCATION with multiple parents but it doesn't work.

    I wish someone could tell me how to assign an HVAC asset to a location that is associated with an HVAC system and then have an electrical asset that is assigned to the same location but associated to an ELECTRICAL system and how would you enter a work order for each asset and yet split the costs according to the systems.

    ------------------------------
    Roberto Landero
    ------------------------------

    Original Message


  • 4.  RE: Difference between location hierarchy vs. other hierarchies

    Posted Mon October 18, 2021 11:10 AM
    Sorry User1971 for starting a new thread of your original article.

    HI Roberto, In Locations Manage Systems.
    1. Create a new system NETWORK and mark as Network
    2. Create a new location of type Operating called NET01 and use Associate System With Location to link to NETWORK system
    3. Duplicate NET01 and create NET02 - these will both be parent locations
    4. Duplicate NET02 and create NETCHILD - the child location
    5. On NETCHILD use New Row in Parent of NETCHILD in NETWORK System and add NET01
    6. On NETCHILD use New Row in Parent of NETCHILD in NETWORK System and add NET02

    There is no issue on creating this on my system, if you repeat and find an issue then you should open a case with IBM Support.

    With regard to the other part of your question you break down the HVAC location to the next level to cover the two systems and assign component assets according to the locations systems or to the parent location. Currently to split out work costs you do need to break down either the locations or assets.



    ------------------------------
    Andrew Jeffery
    ------------------------------

    Original Message


Related Content