Integration Service is designed to work as an extension of Prevu3D’s Asset Service. As a result, there are some entities that are defined in Integration Service directly and there are some entities that are defined in Asset Service. This document aims to provide a quick reference that list the different keys entities, where they belong, what are their uses and how they interact together.
Key Concepts
The entities that belong to Asset Service that are important for Integration Service are the following :
Asset Types
Assets
Integration Links
Integration Server
The entity that belong to Integration Service and that is used for configuration is the following :
Data Sources
Entities Definitions
Assets
An Asset is the logical representation of a physical object within RealityPlan or RealityTwin. It has a 3d representation that is mapped to an actual object within the point cloud. It also contain properties that are related to what the physical object is. For example, a “Pump” asset might have a specific Id, a flow rate, a motor duty, and a 3d representation that define where it is physically located in a plant.
Asset Types
Asset Types are asset templates. They are used to group assets that are similar together. Properties that are defined in an Asset Type will also exist on assets that are derived from them. For example, a “Pump” asset type might specify that derived pump assets should have a flow rate, motor duty and an equipment Id.
Integration Servers
Integration Servers are the logical representation of an Integration Service deployment. It gives Asset Service information about the integration servers that are available for a specific site. The Integration Servers might be on premise in a company’s physical servers or private cloud, or it can be hosted by Prevu3D as part of the SAAS solution.
Integration Links
Integration Links is an entity that is attached to an Asset Type. It create the logical bridge between an Asset Type and data that should be retrieved from a Data Source. The integration link contain information about the data that needs to be retrieved from a specific data source, along with where the parameters that are required to fetch this data are located on the assets that will be derived from an asset type. Each integration link represent a specific set of data that will be extracted from a specific data source for an asset that will be created from an asset type.
Data Sources
Data Sources represent an external data source that the integration service is able to fetch data from. For example, a data source could be an external HTTP API, an Aveva PI Server, a SQL Server or an AWS IoT SiteWise Deployment.