Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Asset Information Management

2D Hotspotting Configuration

  • Last UpdatedOct 03, 2024
  • 4 minute read

The Gateway for 2D Data is used to process 2D data, such as AutoCAD or MicroStation. However, in order to be able to display the hotspotting in them, we need to prepare a configuration accordingly using the Registers Gateway.

Whenever 2D documents are uploaded, data is scraped from these drawings as per the out of the box patterns file present in the cloud.

If we need to push special custom pattern files, please refer to the section Gateway for 2D Data.

Workflow

There are two ways to generate associations between documents and tags. First one is by using the Discovery register and second one is by using the explicit doc-tag association register.

Note: generally, we use both registers to create the document-tag associations. However, we can also use Discovery or Explicit register alone.

When pushing 2D data to the cloud, we use the GDP:

  • .dgn, .dwg and/or .pdf, docx files.

  • The ingestion parameters related to MicroStation, AutoCAD, Data Extractor or 2D document gateways are:

    • PublishReference= true: Scrapes the data present on drawing file and generates the csv file in the cloud that has the scraped content, it also has columns documentid and referenceid (scraped content as per patterns). Whenever you set this as true, also pass the registerId in the Ingestion parameter.

    • Publishrendition = true: Convert the processed file into a simpler form like .svg. When using the Data Extractor, set this parameter to false.

    • PublishOriginal = false: the Gateway for 2D Data will not produce the original file. When using The Data Extractor set this parameter to true.

  • The configurations to create associations between docid and referenceid will be supplied on the clib and it will work against the register ID (Discovery).

  • The explicit doc tag association register configuration on the class library, also called Engineered register.

  • DocTagAssociation.xlsx input file supplied through GDP that contains the list of documents and tags.

Registers Gateway Configuration

Discovery register

The discovery Register is a register which gets created in the cloud after scraping the data based on patterns. The input for this register, generated due to scraping will be automatically picked up from the cloud and passed on to the Registers Gateway as an input register.

The Registers Gateway will use the document and tags primary registers as input to create the association. Before you create the association ensure that Tags and docs are already classified and loaded in system.

Parameter PublishReference needs to be set to true and a registerId needs to be given to use the Discovery register and specify a register identifier in GDP. For example:

Engineered list (explicit association)

This register will create an association between documents and tags. Before you create the association ensure that Tags and docs are already classified and loaded in system.

DocTagAssociation.xlsx input file supplied through GDP must have the document and Tag ID.

For more information on loading files, see Ingestion API Request Parameters.

TitleResults for “How to create a CRG?”Also Available in