{"id":3665,"date":"2017-09-08T23:37:53","date_gmt":"2017-09-08T15:37:53","guid":{"rendered":"http:\/\/localhost\/help\/?page_id=3665"},"modified":"2025-05-08T15:39:26","modified_gmt":"2025-05-08T07:39:26","slug":"templates","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/p2-server\/primers\/templates\/","title":{"rendered":"Templates"},"content":{"rendered":"

<\/p>\n

This article provides general information about templates in IFS OI Server. For instructions on how to create templates, see: \u00a0Creating Templates and Attributes<\/a>.<\/p>\n

A template<\/em> in IFS OI Server is a way of defining the characteristics (attributes) of an entity, where an entity is a real world object (such as a pump) or a conceptual object (such as an area).<\/p>\n

For example, an organisation may have a number of wells. Some wells produce oil while other wells produce gas. Instinctively, we can understand that oil producing wells share a number of characteristics that we want to model, whereas gas producing wells have a different set of characteristics that we care about.<\/p>\n

The grouping of characteristics of a well is called a \u201ctemplate\u201d. In the above example, we have an Oil Producing Well<\/em> Template and a Gas Producing Well<\/em> Template.<\/p>\n

Related: Entities<\/a><\/p>\n

\"Blog_RunTickets\"Templates are a useful tool to help us model what each entity (e.g. well, field, pump) is in the real world. When we assign a template to all of the entities in the system that are of that type, we now have a very robust way of searching for, or processing information about all of the entities of that type. For example, in IFS OI Sentinel we can easily set up a monitor to scan the entire hierarchy, and monitor the Tubing Head Pressure of all Oil Producing Wells. As wells are added and removed over time, these are automatically added or removed from the items to be monitored. This is one of the more compelling advantages of modelling your entities with templates \u2013 you can configure 1 Sentinel monitor and you can watch all 5000 of your wells!<\/p>\n

All entities that are assigned a template take on the attributes of that template. For example, all Oil Producing Well<\/em><\/strong> templates will have attributes like Tubing Head Pressure, Tubing Head Temperature, <\/em>and Choke Position<\/em>; whereas Water Injection Wells<\/strong> might have Injection Pressure, Annulus Pressure<\/em>, and Water Flowrate<\/em>.<\/p>\n

Related: Attributes<\/a><\/p>\n

Consider this example:<\/p>\n

For a typical site with 50,000-500,000 tags that all look like \"AAOW04PS2.PV\", it quickly becomes very difficult find the data you want. To get a complete picture of a well from a historian you would need a list of 50 such tags. If you wanted to build a reporting display for each of the 1000 wells, this quickly becomes unmanageable. Templates allow you to more easily map and model the data coming from these wells by identifying points of commonality and allowing data values to be swapped in and out of those touchpoints, depending on the entity being looked at.<\/p>\n

Here is a simplified example of an asset model with templates and attributes:<\/p>\n\n\n\n\n\n\n
Template<\/strong><\/td>\nAttributes<\/strong><\/td>\n<\/tr>\n
\n

Oil Producing Well<\/p>\n<\/td>\n

\n
    \n
  • Tubing Head Pressure<\/li>\n
  • Casing Pressure<\/li>\n
  • Choke Position<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
\n

Water Injection Well<\/p>\n<\/td>\n

\n
    \n
  • Injection Pressure<\/li>\n
  • Water Flowrate<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
\n

Gas Producing Well<\/p>\n<\/td>\n

\n