An Operating LocationA physical place where assets exist and where work can be performed. More is created in the Locations application and most if not all the location records found will be of type OPERATING. It is the one type of location that can be added to one or more location systemsA Location System is a set of operating locations joined together to form a hierarchy or a network. More, either a location hierarchy or a location network, where an operating location can have multiple parents.

An operating location is a place where one or multiple assets will be found. Like assets, these are core records which are referenced in many applications, work can be performed at an operating location, meter readings can be recorded against a location, a location can be classified and have a specification of attributes, safety information can be added to a location, a location can reference a Rotating Item. An operating location has many similarities with assets, but there are also differences, for example a location does not have downtime. 

An operating location that references a rotating item can only have one asset of the same rotating item at that location. It is saying this functional location requires one asset of a certain type or an alternate item. An operating location that references a rotating item can have an item assembly structure applied. If the item assembly are rotating items, then this creates a location hierarchy at the location where the item assembly structure is applied. 

Operating LocationsA location with a location type of OPERATING. More are defined at the SiteA structural element of a Maximo database that is used for data separation. More level. When you insert and save, a record is added to both the LOCATIONS and the LOCOPER tables. Some of the fields like Calendar, Shift, Failure ClassA Failure Class is the top-level Failure Code of a Failure Hierarchy. More, Meter GroupA Meter Group is a set of meters and can include all three meter types. More, Priority and Rotating Item persist in the LOCOPER table, they exist in the LOCATIONS object but are non-persistent.