Working with IMPACT on multiple databases - guidelines

Last modified by Peter Karlsson on 2022/01/21 12:19

General

If all the stakeholders in an IMPACT project aren’t sharing the same IMPACT database this guide is done to describe the best practice on how to work.

All design by the same (external) consultant

If all design takes place with one design and one Production server. Within in this workflow all new elements are created from the design server and then exported to the production server. In this way, all elements id will be copied from design to production and be the same in both. 

1642762803357-512.png

Figure 1: All design by one consultant only.

Workflow

Abbreviations: Project Manager [PM]

Conditions: Both design and production works with the same design standard.

  1. Start up
    1. The Designer exports the project [PM]
    2. The Project manager imports the project [PM]
  2. At every delivery from design
    1. The Designer exports the project [PM]
    2. The Project Manager imports the project [PM]
      Since the project already exists, it will automatically be an update.
  3. If necessary
    1. The Project manager exports planning [PM]
    2. The Designer import planning [PM]

Element that are planned for production will not be removed from the production server even if they are removed by the Designer.

It is possible to import drawings when working with this workflow.

After this, check the log file so everything looks fine.  

1642763003365-226.png
Figure 2: Log file with several elements deleted but not removed.

Id 10-15 have been removed by design but have not been removed in the production server because they are planned. These IDs must be deleted manually on the production server.

Shared design

If design takes place in several places, for example at several consultants or a factory and a consultant, export element mark must be used to export to the production server. Then an element id on the same element will be different in the different databases (However, the GUID will always be the same).

1642763056718-396.png
Figure 3: Shared design.

Workflow

Abbreviations: Project Manager [PM]

Conditions: Both design and production works with the same design standard and the Project is named the same in all databases.

  1. Start up
    1. Design (one of the design locations) export the project [PM]
    2. The other design location and the Project manager at the production site imports the project [PM]
  2. At every delivery from design
    1. Design exports new/changed components [PM]
    2. Design exports the new/changed element marks [PM]
    3. The Project manager (at the production site)/design (other location) imports possible new/changed components [PM]
    4. The Project manager (at the production site) /design (other location) imports possible new/changed element marks [PM]
  3. If necessary
    1. The Project manager exports planning [PM]
    2. The Designers (both locations) import planning [PM]

It is possible to import drawings when working with this workflow.

After this, check the log file so everything looks fine. 

1642763148397-884.png
Figure 4: Log file with new, removed and updated elements.

Id 626 is removed.
Id 627 (W101) is new.
Id 628-631, 633 and 636 are updated (New element mark, new measurements, etc.).

1642763246555-192.png

Figure 5: Log file with new elements with different ids.

Id 780-789 is new and have received different element id than at the design location where they were created.

Shared production

If production takes place in several places, for example if one or several factories is helping another producing factory out with production of elements, export as linked needs to be used to export to the production servers than has a non-matching design standard. Then an element id on the same element will be different in the different databases (However, the GUID will always be the same).

Workflow

Abbreviations: Project Manager [PM]

  1. Start up
    1. Design creates the project in the design standard of the main production factory [PM].
    2. The supporting production factory/ies creates the project in their design standard [PM]. (Same project name is not necessary)
  2. At every delivery from design
    1. Design exports the new/changed elements as linked [PM]
    2. The Project manager (supporting production factory/ies) imports possible new/changed elements [PM]

It is not possible to import drawings when working with this workflow.

Check the log file so that everything looks correct.

1642763400072-816.png

Figure 6: Log file from imported linked first time.

First import shows all element as created it also displayed what components has been imported.

1642763455159-650.png

Figure 7: Log file from imported linked second time.

After removing some sandwich walls in design and then made a new linked exported. The log above is when they are imported in the supporting producing factory.

Element that are planned for production will not be removed from the production server even if they are removed by the other factory.

It’s not possible to import planning between different standards and project, sharing “Rough Planning” should be done with an Excel Sheet and copied into PM.

The communication between the main production factory and design can work as described in the chapters All design by the same (external) consultant, Shared design depending on which alternative apply.

Element Id the common thread throughout the process 

In order to create an early erection plan and a coarse planning of the casting and transports, a 3D model (Project planning document) should be created early. Thereafter during the fine project planning and editing of the design, it is crucial to keep the element's id since these are keeping all the information about the production planning.

cb1.png
Figure 8: A model in Project Manager.

If you remove an element in the model and replace it with a new one, then the new element automatically gets a new id and the production planning information is removed. In order to prevent this, use one of the following commands:

  • Edit
     
  • Save As
     
  • Replace
     
  • Rename

Element Id

In AutoCAD under Plan -> Settings Plan, you can switch on/off several settings, among others the Element Id.

cb2.png
Figure 9: Settings Plan…

cb3.png
Figure 10: In Settings Plan, the Element id box can be found.

The Element id is shown under the element mark.

cb4.png
Figure 11: Element id in AutoCAD.

In the Model Viewer, the element id is shown in the Properties dialog when the element is selected.

cb5.png
Figure 12: Element id under properties in Project Manager.

Edit element

Edit element does not change the element id.

Example:

Before a recess:

cb6.png
Figure 13: Element id before a change.

After a recess:

cb7.png
Figure 14: Element id is kept after a change.

Save As

Save as, with a new element mark, does not change the element id.

Example:

Before:

cb8.png
Figure 15: Element id with the element mark 1.

After:

cb9.png
Figure 16: Element id is unchanged with the new element mark 2.

Replace

Replace, with a new element mark, does not change the element id.

Example:

Before:

cb10.png
Figure 17: Element id is unchanged with the element mark SLABA.

After:

cb11.png
Figure 18: Element id is unchanged with the element mark SLABD.

Do not remove an element first, and then do an Insert afterward, this will change the element id.

cb12.png
Figure 19: Element id is changed due to an insert.

Rename

Rename of an element mark does not change the element id.

The element mark can be changed in either Project Manager or AutoCAD (See Save As for AutoCAD).

How to change the name in Project Manager:

cb13a.png
Figure 20: Rename of SLABC in Project Manager -> Element Marks.

After this step, you need to return to AutoCAD and run “update plan”.

cb14.png
Figure 21: SLABC will be renamed to SLABF, note the element id.

cb15a.pngData URI imagecb15b.png
Figure 22: Update plan in AutoCAD -> Plan -> Update plan.

This will change the element mark but not the element id.

cb16.png

Figure 23: SLABC is now renamed to SLABF, note that the element id is still the same.

Definitions

Explanation of some crucial terms. 

Production Server

The IMPACT server that contains the database with all the production planning.

Design Server

The IMPACT server or servers that contain databases with all or part of the design.

Design standard

A set of products, templates etc. that the project will use. The design standard needs to be the same in all databases, for instance 1101.

Production company

All companies working with production and project planning in IMPACT has a production company. The design standard can only be linked to one production company. In the example below the design standard 1100 is connected to the production company 1011.
1642763763233-945.png

Figure 24: Hirearchy of Production company and Design standard in IMPACT Standard Admin.

Project name

The name of the project, maximum 12 symbols. It must be the same in all databases.

Rough planning

Elements that are not found on the cast bed or on a transport.

Fine planning

Elements that are found on the cast bed or on a transport.

GUID

Globally Unique Identifier. The elements social security number
(for example F4BA8C39-B610-4E74-A855-7AF301C776FA)

Element Id

An elements unique number in a project.
(E.g. 321)

Element Mark

Elements sharing the same properties can be using the same element mark. This indicates that they can be casted in the same mold.

(for example W1001). Please note that one element mark may be connected to several element ids.
(E.g. W1001 (Id 1), W1001 (Id 2))

 

Tags:
Copyright 2024 StruSoft AB
IMPACT Wiki