IBM Asset & Facilities Management Your destination for peer and expert insights to help unlock the power of data with AI and Asset & Facilities Management to advance your digital reinvention. Join / Log in
We currently are on Maximo 7.6.We are working on setting up data for our Water Meters for our clients, including Residential (Individual and Multi) and Commercial (Individual and Multi) clientsWe discussed that the Water Meters will be on Service Addresses, so that we do not have to end-up with thousands of Locations.Where we are struggling is that how to handle multiple Service Points at one Service Address... We are being asked that for this, we need to have Locations for Service Address... which translates into thousands of Locations... the same issue is for our Waste Collection Bins, which might add more bulk Locations... as Waste Collection bins are also on Service Address... so same issue will come for that design also
Please provide some guidance, so that how can we avoid having to create thousands of Locations and just stay with Service Addresses
Hi MX ProI would be creating Locations for each service point. This should be aligned to your billing / CRM solution to simplify reconciliation.You need to be careful of older buildings that have a single meter that is shared across all lots. That is, each unit does not have an individual meter, therefore billing is done as an apportionment of the lot in relation to the rest of the lots in the building.Good luck!
The issue with creating locations, as I mentioned in my original post, is that this will result in thousands of locations, which we wanna avoidThanks for replying anyways...
IMO you may find that taking advantage of the functionality that is already inherent to Maximo, specifically Meters on Locations, Locations within Address Systems, etc. will have greater benefit than the cost/effort of the many Location records you will end up with. Given a Service Address can have many Locations related (Meters, Waste bins, etc.) and then those Locations having Meters related to them, you may find that provides a structure that will suit you for years to come. A well thought out Location hierarchy is a key foundational element of a Maximo implementation. Hope this is of some help.
Keep the location as your service address, and build an asset for each service point under the location? Either way, you'll have thousands of records. But at least you'll protect the location = service address relationship.
I'm echoing everyone else here so far, but here are my few cents:We're a new Maximo customer, currently implementing MAS 8 and Manage for the first time. We use Oracle C2M for our billing system and a home-built app for development projects and service points, which are integrated with our GIS platform (ESRI utility network). Using Maximo Spatial, we are pulling service points over as locations, and they are rolling up to a single parent location in a separate system from our other locations. This is keeping it pretty clean and tidy for us so far. An advantage here is that we can link meters to the SP locations as assets as well as other SP-specific assets, such as Backflow Prevention devices.Not sure if that helps, but figured I'd share our approach. It's proving to be pretty powerful when it comes to how the data will be managed.