A tag name is not an asset. PLANT2.U3.BRG.VIB.01 means something to the engineer who configured it in 2011 and nothing to anyone else — not to a new hire, not to a reporting tool, and not to a machine-learning model. The AVEVA PI Asset Framework is where that institutional knowledge becomes structure the whole organisation can use.

Most PI estates have an AF model. Far fewer have one that is complete, consistently templated, and trusted enough to build on. LAMR designs and rebuilds AF models so they describe the plant as it exists today and keep describing it as the plant changes.

What we do

  • Asset hierarchy design. A structure that mirrors how your organisation actually reasons about plant — site, unit, train, equipment — rather than how the historian happened to be commissioned.
  • Template engineering. Element templates with inherited attributes, so a new compressor is onboarded in minutes and every compressor answers the same questions the same way.
  • Attribute mapping. PI point references, table lookups, formula attributes and unit-of-measure enforcement, with engineering units defined once rather than negotiated per report.
  • Analyses and calculations. Rollups, performance equations, availability and efficiency calculations, expressed at template level so they apply across the fleet.
  • Event frames. Capturing batches, trips, startups, excursions and outages as first-class objects you can compare against each other rather than as regions on a trend.
  • External context. Bringing maintenance records, lab results and asset registers alongside process data, so a signal can be traced to a cause.

Why the model is the asset

Every downstream capability inherits the quality of the AF model. Dashboards built on an inconsistent hierarchy need rebuilding per site. Analytics trained on unmapped tags learn the quirks of one unit and fail on the next. Cloud and lakehouse programmes that lift tags without carrying context produce an expensive archive rather than a data product — the single most common and most costly mistake we are asked to correct.

Done properly, an engineer can ask for bearing vibration across every Unit 3 class asset without knowing a single tag name, and the answer means the same thing at every site.

How we work

We start from the plant and the people who run it, not from the existing tag list. Where an AF model already exists we assess it first and rebuild only what needs rebuilding. Templates, naming standards and documentation are handed over so your own team can extend the model without calling us — the measure of a good engagement is that it ends.