Entities are the backbone of all data in IFS OI Server, and represents the objects in your world that you want to gather information about. These can be real world objects, like a well or pump, or they can be things that are known by convention, such as an area, or business unit. \u00a0<\/p>\n
![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2015\/05\/model3.png\")
<\/a>Entities being modelled in a hierarchy<\/p><\/div>\n
Entities are added to\u00a0hierarchies, to represent the relationships between them. For example, we can have entities that represent a well, or a country, or a pump. You can put entities into a hierarchy to organise them in a way that makes sense for your organisation.<\/p>\n
Entities have attributes, which represent specific aspects of the thing we are concerned with. For example, we may have an entity that represents a well, and the well has several aspects that we care about, such as Flow Rate, Choke, and Tubing Head Pressure.<\/p>\n
Name<\/strong><\/td>\n| Display Name<\/strong><\/td>\n | Description<\/strong><\/td>\n<\/tr>\n | Western Australia<\/td>\n | WA<\/td>\n | WA Business Unit<\/td>\n<\/tr>\n | Pilbara<\/td>\n | Pilbara<\/td>\n | Pilbara Region<\/td>\n<\/tr>\n | Mobile Fleet<\/td>\n | All Mobile Fleet equipment<\/td>\n | Grouping of all Mobile Fleet equipment<\/td>\n<\/tr>\n | Herbert<\/td>\n | Herbert Gas Well<\/td>\n | Herbert Gas Producing Well<\/td>\n<\/tr>\n | Derby<\/td>\n | Derby Water Well<\/td>\n | Derby Water Injection Well<\/td>\n<\/tr>\n | Hunter<\/td>\n | Hunter Oil Well<\/td>\n | Hunter Oil Producing Well<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n | <\/p>\n System Identifiers<\/h2>\nA key aspect of IFS OI Server is that it is able to pull in and consolidate entities from different systems, from other IFS OI applications such as Procount, Stratus, and P2P, or from other data systems.<\/p>\n One of the issues that people run into when trying to integrate systems is that the same item may be called different things in each of the systems, so how do we keep all of these different names linked up?<\/p>\n In IFS OI Server we do this by using a System Identifier<\/em>. Each entity can have a different name in each data source connected to IFS OIServer.\u00a0 We can then refer to a single entity and IFS OI Server will use the system identifier to understand which entity we are referring to in the underlying source system.<\/p>\n Once these have been set up, IFS OI Server can do some automatic mapping to these systems, for example when running a dataset query:<\/p>\n |