A demo by Simply Impact

Know what you measure

From installation drawings to one dataset your own people have checked. See below how AssetAtlas reads a drawing.

Output.csv

group,object,component,code,quantity,unit
101 Heat pump 1,WP01,Temperature sensor,101TT01,temperature,°C

{
  "code": "101TT01",
  "type": "TemperatureSensor",
  "object": "WP01", "group": "101",
  "measures": { "quantity": "temperature", "unit": "°C" }
}

:101TT01 a brick:Supply_Water_Temperature_Sensor ;
    brick:isPointOf :WP01 ;
    brick:hasUnit unit:DEG_C .
:WP01 a brick:Heat_Pump ;
    brick:isPartOf :system_101 .

ver:"3.0"
id,dis,point,sensor,temp,water,leaving,equipRef,unit
@101TT01,"Supply temp WP01",M,M,M,M,M,@WP01,"°C"

Name     TypeName            Space          Description
101TT01  Temperature sensor  Plant room 1   Supply WP01

asset_tag    ← code       101TT01
asset_class  ← type       TT · temperature
parent       ← object     WP01
eenheid      ← unit       °C

Installation model

You judge

101 · Heat pump 1

101WP01heat pump
101TT01sensor
101CP01pump
101VA01valve
101TT02sensor

102 · Heat pump 2

102WP01heat pump
102TT01sensor
102CP01pump
102OS01valve

Unclassified

102TSA0

0 pieces read · 0 tags · 0 in doubt

The sheet. The drawing is too large to read in one go. First it is prepared as an image.

The problem

Why the signals alone are not enough

Your building-management system sends signals all day: a code and a number. What it does not send is which part of the installation each signal belongs to. That link lives only on the drawing, and a drawing is a picture.

Live signals

a code and a number

no one-to-one match

The parts

pumps, sensors and valves

The drawing

the only thing that ties them

Reading it

takes a specialist, and they are scarce

The question

How do you get that link for every signal, without waiting on one scarce specialist, and in a way your own people can check?

The solution

The machine reads, a person decides

AssetAtlas reads the drawing in small pieces that each keep their address. A person from your side judges every value.

Machine work

Human work

1The sheetone large sheet
2Pieces with an addressoverlapping, nothing skipped
3Reading tagseach piece on its own
4Rereading doubtup close, once more
5A tree, not a listduplicates out, in groups
6You judgeapproved, wrong or corrected

The result

One row per measuring point

You get back a dataset: per measuring point the code from the drawing, what it is, what it measures and the link to the live signal. Someone from your side has judged every row.

Code: 101TT01
What it is: Temperature sensor on the supply of heat pump WP01
Measures: Temperature, in °C
Live signal: Linked to the signal with the same code in the BMS
Reviewed: Approved

On the left a part of the example sheet with one code circled, on the right the row it becomes.

Why you can rely on it

Checkable, not magic

Every code has an address
Every piece remembers where on the sheet it came from. Click a part and you see it on the drawing.
Doubt is written down
What is not certain is not guessed or smoothed over. It is listed as 'unclassified', with its place on the sheet.
A person has the last word
Nothing leaves AssetAtlas before someone from your side has judged every value.

What to expect

5 drawings per workspace; more on request.
Uploads and results are deleted automatically after 30 days. You can delete everything yourself at any time.
Processing and storage in the EU (Scaleway); no training on your drawings.
A demo without an SLA: meant to try, not to build on.

Try it on your own drawing

Upload a P&ID as PDF, up to 20 pages and 25 MB. You see the same replay with your own result.

Try for free