What is BECS Dynamic Packaged Integration (BECS DPI)?
BECS Dynamic Packaged Integration is new integration predefined solution enabling visualization of external user enterprise system data via BECS integration. This solution is deployed as easy to use preconfigured way of “on demand” (on fly) data visualization from any BECS connectable user enterprise system or Bentley product as well as visually filter displayed 3D model by querying the data across all BECS integrated enterprise systems.
What are the main parts of BECS DPI?
BECS Dynamic Packaged Integration consists of following main parts:
|
BDPI Component |
Short Description |
|
BDPI EndPoint |
Service endpoint for initiating the BDPI integration processes |
|
BECS Dispatcher Project |
BECS Integration project initiated by calling the BDPI EndPoint call and resolving the proper execution of relevant dataReading Project |
|
BECS dataReading Project |
BECS Integration Project designed for concrete enterprise system (BDPI need to be updated with every dataReading Projects for each enterprise system planned to connect. |
|
BECS Temporary data Cache |
BECS internal data storage for saving the data during the transmission, processing them to requested / filtered format by BECS Selection Console before packaging to json format as payload for iTwin caller |
|
BECS Web Admin Console |
BECS Web Portal provided with BDPI for administering all details of BDPI integration solution |
|
BECS Selection Console |
Part of BECS Web Admin Console dedicated for easy selection, renaming and packaging the attributes taken by any of BECS dataReading projects |
The picture below shows the BECS DPI general solution architecture:
How BECS DPI works?
General principle of BECS DPI integration with any iTwin product (for example PlantSight, WaterSight, SYNCHRO, OpenComms, etc.) is in definition of one single end point for each iModel (BECS DPI end point). This end point is initiating BECS_Dispatcher integration project, which is authorizing initiated call and via BECS mapping console is resolving which BECS dataReading project to load and execute.
Data retrieved from dataReading project are filtered by actual attribute selection done by configuration administrator in BECS Selection Console and final dataset is packed into .json and sent as a payload to original iTwin application.
Actual visualizer ways for BECS DPI
Standard implementation of BECS DPI enables following ways of interaction with iTwin/PlantSight visualizer (BECS DPI solution is adapted by now only for iTwin/PlantSight visualizer component):
- Property data visualization
This option enables to visualize external BECS taken data in a form of Properties. This kind of data relationship is useful only if BECS enterprise system integration returns one set of data (one row) for selected PlantSight element.
The section’s names as well as assignment of attributes to sections are managed in BECS DPI Web Admin Console.
- Multi line TAB visualization
For sharing the “multi line” data taken from integrated enterprise systems (such as SAP Work Orders, SharePoint or ALIM Documents, EasyRisk data, etc.) are enabled by Multi line TAB visualization.
The TAB names as well as assignment of attributes to TAB are managed in BECS DPI Web Admin Console.
- Visual Filter
BECS DPI enables to define Visual Query filter across BECS integrated enterprise systems and display result as filtered and zoomed in standard visualizer 3D view.
This functionality supports also coloring of result by any of integrated attribute.
The list of attributes for building the query and coloring result are managed in BECS DPI Web Admin Console.
Sample of this functionality:
To keep solution flexible and open we designed BDPI Web Admin Console as a Admin Portal place where responsible solution Admin can manage all aspects of BDPI integration on fly. From enabling of any new integration, via selection of displayed attributes, user naming of them, making custom sections for keeping logical attributes sorted in Bentley DigitalTwin visualizer up to selection of attributes for Query builder, custom colour sets and ranges for colouring and blinking:
BECS Dynamic is also very strong in generating “on-fly” reports from fresh data, which are displayed in standard PiP functionality of PlantSight visualizer. Thanks to this can be generated well formatted pages from “list of ShaePoint documents”, via details from almost any external information system (SAP or Maximo WorkOrders details, StreetView of Google…) up to the IoT reports or DashBoards…
The video below shows the main features of BECS Dynamic Packaged Integration used in PlantSight - how to visually integrate without any hard-coding or modification on PlantSight side with any enterprise systems or its combinations.
In this example data are dynamically loaded to PlantSight Properties window from the selected systems (SAP, Maximo, APM/AR, ALIM,…) by BECS without any saving on PlantSight side. BECS also generates on fly Multi line tables (SAP Work Orders, SharePoint documents, ALIM documents, AR/APM alarms,…) to the selected element in PlantSight. Visual Filtering in PlantSight by BECS dynamic data retrieve enables to filter across external enterprise systems within one filtering condition, e.g. attribute name from SAP (Manufacturer,…), approved construction in SharePoint, approval status in ALIM and coloring by selected attribute (e.g. country of manufacturer, acquisition date,…) at the same time. Data are always fresh and taken directly from source systems and displayed without any saving. BECS Selection Console enables to add any new system to PlantSight Properties window or selection and adding the attributes for Multi line Tables or Visual Filtering with no need of programming.
How to find a ready to use BECS Dynamic Packaged Integration?