Brief summary of BECS PlantSight Integration
iTwin and its industrial child PlantSight brings new quality of making and using DigitalTwin solution. But every solution can be only as good as good is integration of this solution into existing user enterprise.
BECS, as widely used powerful Bentley integration platform, enables integration of PlantSight with any user enterprise system from ERP (SAP, Oracle eAM, IBM Maximo,…) via DMS (Documentum, OpenText, SharePoint,…) to GIS (ESRI, AutoDesk, Hexagon,…) or IoT.
BECS currently supports several integration options for PlantSight, implemented in relevant BECS PlantSight integration packages (described below).
What is BECS Packaged Integration for PlantSight
In general, BECS Packaged Integration is a ready to use solution package covering concrete pre-defined workflows between different enterprise systems, running on BECS technology.
BECS Packaged Integration for PlantSight is a solution package to connect the world of PlantSight on one side with any user enterprise systems or its combinations on second side, regardless of whether they are from Bentley application family or a third-party product family.
Currently, you can choose from these four BECS Packaged Integration options for PlantSight (see the details of each by clicking at the link below):
- BECS Packaged Integration for PS via Interop
- BECS Packaged Integration for PS via Datahub directly
- BECS Dynamic Packaged Integration for PS PiP
- BECS Dynamic Packaged Integration for PS GUI
The differences among the integration packages are described below:
In the first two integration packages (1 & 2) are data of external user systems redundantly saved on PlantSight side. The integration packages directly to PlantSight (3 & 4) are dynamic ways of integration where data are taken and used online right from PlantSight environment.
While the first three integration packages (1 & 2 & 3) are system oriented (these integration packages cover the PlantSight integration with one concrete enterprise system - e.g. SAP or MS SharePoint), the fourth integration package (4) enables PlantSight to integrate with any new enterprise system(s) with no need of configuration or modification on PlantSight side.
The mapping for BECS Packaged Integration for Interop and DataHub is set directly in integration projects used for pre-defined workflows. Therefore, if the user requires different mapping or wants to manage mapping between input business object data and the CCOM representation, it is needed to change them in the relevant BECS Integration Projects.
BECS Dynamic Packaged Integration allows to set the mapping in native BECS mapping web console very easily. The video below shows two main mapping principles used in BECS dynamic integration for PlantSight. In this example is shown the PlantSight integration with SAP and MS SharePoint systems (no data saved in PlantSight).
BECS Visual Filters
The video below shows dynamic functionality of Visual Filtering in PlantSight by BECS dynamic data retrieve, implemented in BECS PlantSight Packaged Dynamic Integration for PS GUI. In the example we will read data from SAP system and filter by them in PlantSight without any saving of data on PlantSight side.