MBM Project
  Home Tribon Utilities Downloads Tribon Articles Tribon Resource Register CAD/CAM Catalog Tribon Forum Old forum
New Articles: # Check PDMS Guides and PDMS / Tribon comparison

TB Project Handle

Tribon M3 introduces new way for Tribon data exchange between shipyards, design offices and subcontractors. M3 Project Copy simplifies the task of Tribon model transfer (objects copy) between different projects and reusing existing Tribon model in new projects.

TB Project Handle is based on Tribon M3 Project Copy API and provides some extended functionality and comfortable user interface. Advanced control, automation and two levels of protection against unwanted data overwriting during the import procedures are combined with intuitive interface. When running in "Import" mode for example it provides some preliminary information about the selected transfer set status and contents details. Some common controls like "Log Report Form", "Task Scheduling", etc. are available directly at the startup window.

TB Project Handle implements the following additional features:

  • possibility to select all Tribon object types at once and at the same time to be able to assign different selection filters for different object types
  • multiple selection filters for one and the same object type within one object collection session
  • auto extend functionality - identifies and collects all referent objects automatically
  • implements collection templates - set of object selection methods, criteria and transfer options that can be stored and reused for repetitive data transfer
  • referent objects identification
  • transfer log report form
  • data import simulation - when transferring information from one Tribon project, design office or subcontractor to another, one of the most important issue is to get clear picture about the contents of the transfer set and its correlation with the target project. This function indicates which objects are new and which objects already exists in the target project.
  • object protection list - working with subcontractors involves Tribon data exchange on regular basis. One Tribon transfer set will often include objects that should not be overwritten in the receiving site/project. This function helps to protect Tribon data specific to the destination site/project from accidental overwriting during the import procedures
  • task scheduling - it might take a long time to create one Tribon data transfer set, especially when big number of objects is involved. What about if more than one transfer set is required? Schedule all data transfer jobs for the night...

Tribon objects type selection

TB Project Handle provides advanced method for collecting the different Tribon objects types that have to be included in one transfer set collection. It is possible to mark for inclusion in the collection more than one object type and collect all data at once. Select all Tribon types required in the transfer set and specify their corresponding selection criteria/filter, then click "Add Objects" once to create the collection. (see example screen shot)

Multiple selection filters

It is possible to specify more that one selection filter in the object name field. For example to get all outfitting model objects (pipe, cable, cable way, ventilation , structure and equipment) for modules MOD1, MOD2, MOD31, MOD32... just right click in the outfitting tab area and select "Select Outfitting Model" from the context menu. Then key in the module names in the module field separated by blank space "MOD1 MOD2 MOD3*". This way all outfitting model objects for the above mentioned modules will be included in the collection with just one or two mouse clicks. (see example screen shot)

Auto extend

Automatically extend collected model objects with their referent objects. One cable way for example may have the following referent objects: cables routed on the cable way, components used for material, structure parts, other connected cable ways, assembly references. When auto extend function is checked, all referent objects will be automatically included in the collection even if they are outside the scope of the current selection criteria.

Collection templates

In M3 Project Copy it is possible to save the current transfer set collection for further usage. However, it is not very likely to be able to reuse the same collection set again let say one week later when will be necessary to export the same blocks/modules again but lots of new objects have been created meanwhile. The previously stored collection will not include the new objects created afterwards.

TB Project Handle provides additional approach in handling similar repetitive tasks. It uses collection criteria templates and generates the transfer collection set dynamically. This way an updated Tribon transfer set representing the same area will be created where the new objects will be included automatically. The template will store and reuse the same transfer options' settings as well.

Referent objects identification

Tribon objects references are one important detail to be considered when transferring Tribon data. M3 Project Copy provides "Extend selected" and "Extend all" functions as a possibility to include referred objects in the collection. Once the referent object becomes included in the collection, there is no way to be identified as a referent object afterwards. This functionality prevents from duplicating objects in the collection, but also decreases the possibilities to analyze the objects included in the collection and their references.

TB Project Handle makes it possible to identify these objects references regardless whether the referent object has been included in the collection or not. The usage of this functionality extends to Tribon project data maintenance and recovery activities as well, as it is a source of valuable information for Tribon model topology structure. (see example screen shot)

Transfer Log report form

Tribon M3 Project Copy generates XML log file as a result of every data transfer procedure. The file consists of detailed and useful information about the status of the transfer set, but for large data collection it becomes difficult to be used.

TB Project Handle provides special transfer log report form, where the information from log files is collected, divided by categories and summarized, which makes it easy to be analyzed. (see example screen shot)

Data Import Simulation

In one real Tribon project environment the creation of one transfer set involves big number of objects and different object type. Very often different people are responsible for the objects from different areas or different type. Thus, collecting and exporting the required information might become an not easy task. In this respect while the person who is exporting the data is collecting all objects required, their references and the references of the referent objects (no mistake, some time you might need to "Extend" the collection twice or three times in order to get all objects involved) it is very likely that in the collection will be included objects that are not required or even unwanted at the target project.

When importing any transfer set, TB Project Handle feature "Import Simulation" will help you to identify which objects already exists in the target project, and might be overwritten, and which objects are new for this project. Then it is easy to exclude some or all of the existing objects from this collection, preventing any overwriting of valuable data. (see example screen shot)

Object Protection List

Exchanging Tribon data between shipyards, design offices and subcontractors could be quite sensitive process in terms of protecting your own data from unwanted overwriting. Sharing one Tribon project between two or more parties involves exchanging data on regular basis. At some project stage every party will need to import Tribon data created at the other sites. When transferring part of one Tribon project to/from subcontractor, the transfer set may consists of old versions of objects that already exists at the target (receiving) site. Some of these objects might be required but some of them might be unwanted as they could represent just an old versions of the current data at the receiving site.

To protect your Tribon data and avoid unwanted data overwriting on top of Import Simulation TB Project Handle Implements Object Protection Lists.

The object protection lists can be easy created and updated directly from MBM Project Copy program interface. Unlimited number of lists is supported. Every list can serve different subcontractor or specific task or model area. Right before importing the new data to your project, load the object protection lists and activate them. All objects included in the collection (that you are going to import) that exists in any of the activated object protection lists will be marked as protected. Then it is your choice to decide whether to exclude protected objects from current collection or not. (see example screen shot)

Transfer task scheduling

The process of Tribon transfer set creation could be divided on two parts:

  • collect data - create the transfer collection, which involves finding and verifying the objects that will be transferred
  • copy data - copy collected objects to transfer set data base

While the first part of the job could be done in relatively short time, the process of data copy could take quite long time. It depends on several factors like: system performance, object types involved and the number of objects to be transferred.

TB Project Handle task scheduling feature can save lots of the time required for data collection and transfer set preparation. Three methods could be used to prepare the collection:

  • all objects
  • stored collection - previously created and stored collection
  • stored template - previously created and stored template

It is possible to schedule one or more different tasks (Export, Import, Verify) targeting different Tribon projects. Since it is never known how long one task will be running, TB Project Handle suspends and queue any coming tasks if the previous one has not been finished. This method guarantees that there will be no task skipped and at the same time it is not necessary to try to predict how long the first task will be running in order to define at what time to schedule the next one. (see example screen shot)

Get evaluation copy

For more information or to request evaluation copy you are welcome to contact us at mbmproject@mbmproject.com





 
Privacy Statement