Splitting the Wiring Design Among Several Teams - Intergraph Smart Instrumentation - Help

Intergraph Smart Instrumentation Help

Language
English
Product
Intergraph Smart Instrumentation
Search by Category
Help
Smart Instrumentation Version
13.1

There are projects in which, for various reasons, several teams work on the wiring design of the same project. These teams can be located at the same site or be in different geographical locations.

A good example of such a project is when the main contractor designs the field instrumentation wiring up to the marshaling racks while the DCS vendor is responsible for the DCS design and for the design of the wiring from the marshaling panels to the terminals of the I/O cards that they supply, as shown below:

PPM All Outputs Graphic

At the end of the project, or at any intermediate stage, there is a need to integrate both designs into one database to complete the wiring from the field to the DCS and then generate the complete loop diagrams and the wiring reports.

At this time, the boundary or the scope of the design that each party is responsible for can vary from project to project. Usually, the intersection point would be somewhere around a marshaling panel, either at the field side of a terminal strip and the control system terminal strip side. This issue is usually discussed between the parties and they agree where to draw this line.

In Smart Instrumentation, we recommend the following strategy to handle this split wiring design:

  1. The main contractor or the EPC starts with the creation of an As-Built domain and then creates a project for each of the working parties involved in the overall design. In the example mentioned above, the main contractor works on the main As-Built plant and defines the projects for the DCS vendors.

  2. All the teams work on the same database using Citrix. However, it is also possible to work offline.

Using this approach for splitting the design has the following advantages:

  • Provides the ability to see the current As-Built data while connecting to the data (and not the other way around).

  • Enables good control of new tag numbers and subcomponents.

  • Retains the uniqueness of rules when adding various subcomponents such as terminals on a terminal strip.

  • Enables the comparison of As-Built loops and project loops.

Note that the members of the various teams working on the projects must be informed of the changes made in As-Built so that they can update their databases. Consequently, based on the data maturity, teams should coordinate among themselves when to transfer their wiring data to the rest of the projects.

For more information, see Owner Operator Domain (As-Built and Projects) in the Administration Module help or in the Smart Instrumentation help, see Working with As-Built and Projects.