Data Migration from P&ID System to SPI

Agenda

 Introduction

− BIO
− AMEC
− This data migration was Independent and external source /third party
software to import directly into the SPI Import Utility

 Configuration and Coordination

- Instrument Types need to match

- Attributes that are mapped

 Oracle Views and SPI Import Module

 Comparison Reports for the Data Migration (Validation)

 Tips and Tricks for the Import

2
Introduction

3
Introduction

 Needed mechanism to transfer data from P&ID system to SPI

 Oracle to Oracle Transfer, alleviates the problems of EXCEL import

- Flags have to be set for the data to come across properly.

- Imports creates extra spaces in fields, sorts incorrectly

- The text fields have to match

 Once, tag and loop data was imported, other EXCEL imports were
used to transfer the data, i.e. UDF fields

 SPI Import Utility to transfer the data

4
Configuration and
Coordination

5
Configuration and Coordination

Visual Data Transfer

P&ID SPI
Data Data

Instrument
Type
Views
Entity SPI Import Module
Number

6
Configuration and Coordination

 The instrument types needed to match exactly between the two

systems
 Transfer in the Oracle Views was based on entity numbers

OILCO

OILCO_IMPORT_TABLE
OILCO_IMPORT_TAGS
OILCO_SPI_INSTR_TYPE
OILCO_SPI_TAGS_FORMATTED
OILCO_TAG_CHECK
OILCO_VPE_TAGS
OILCO_VPE_TAGS_FORMATTED
OILCO_APPENDIX_C

Names of Oracle Views

Details of Oracle Views

7
Configuration and Coordination

 Oracle Views were built to format the tags before the transfer for the
P&ID system and SPI.
 Another Oracle View was used to compare the two sets of tags.
 Other Oracle Views were created to do validation reports.

 The biggest challenge was the work process with the P&ID group to
ensure the data got populated in the database.

 Instrument Engineers have to be involved with the tags and the

instrument type set-up.

8
Configuration and Coordination

 Once the Oracle Views were created, the SPI Import Module can use the view
as a Table Import.

OILCO Import (Package 1)

Usernames and passwords

OILCO_IMPORT_TABLE are set by the Oracle DBA

9
Configuration and Coordination

 Used existing import links that were created for the import.

SPI Import Link

 Can re-use link for each import.

SPI Import Link Name

10
Configuration and Coordination

 Data Attributes and Mapping P&ID - SPI

Process
Function Type

Instrument Type
& Description

P&ID - P&ID
Equipment Description
Name
Line Number

Line Size/Unit

11
Configuration and Coordination

 Data Attributes and Mapping

Tag Name

Loop Name

12
Oracle Views and
SPI Import Module

13
Oracle Views and SPI Import Module

 Oracle Views created based on Entity Numbers and revision

- Tag numbers were manipulated between the two systems in the Oracle Views

- Next view was used to format tags to do comparisons (View used to import table
in SPI Import Module)

- Views to other reports to create Comparison Reports (Reports Highlighted

between two systems)

 SPI Import Module

- SPI module was linked to the Oracle View from the format tag comparison

- Tag and Loop Numbers were created using the P&ID formatted tags (The tag and
loop numbers were then manipulated in the SPI Import Module

- Other fields were mapped using the P&ID mapped fields

14
Oracle Views and SPI Import Module

 Once the source data is configured in the Import Module, we need to define the
instrument types in the Import Module

15
Oracle Views and SPI Import Module

 In the Properties Tab for the Import Module, the instrument types have to
be mapped for each Process Function.

 This mapping will alleviate problems of rejected records if the instrument types
didn’t match.

16
Oracle Views and SPI Import Module

 Also, the new instrument types need to be mapped to the source data

17
Oracle Views and SPI Import Module

The tag and loop names are configured based on the P&ID data segments.

Loop Name was left with a ‘ ‘ for a null segment

18
Comparison Reports
for Validation

19
Comparison Reports for Validation

 SQL Reports were used to compare the data of what is in P&ID system versus SPI.

 Validation Reports :

- All Tags in SPI

- All Tags in P&ID system

- Comparison of SPI and P&ID system

- Instrument Types that match in SPI and P&ID system

- Tags in SPI but not in P&ID system

- Tags in P&ID system but not SPI

20
Comparison Reports for Validation

SPI Tag P&ID

Line Instrument
Name Number Process
Number Type
Function
Type

Report A - All tags in SPI

21
Comparison Reports for Validation

P&ID Tag P&ID Line

Name Number Number

Report B - All tags in P&ID System

22
Comparison Reports for Validation

Line
Number

Tag Instrument P&ID Equip.

Name Type Number Name

Report C – Comparison of SPI and P&ID System Indicates Differences

23
Comparison Reports for Validation

P&ID

P&ID Instr. SPI Instr.

Type Type

Report D – Instrument Types that Match P&ID System and SPI

24
Comparison Reports for Validation

P&ID

P&ID Tags SPI Tags

Report E - Tags NOT in P&ID System but in SPI

25
Comparison Reports for Validation

P&ID

P&ID Tags

Report F - Tags NOT in SPI but in P&ID System

26
Tips and Tricks
for the Import

27
Tips and Tricks for the Import

 Loop Names – Loop Names were generated as a default using the first
character of the Prefix and the Component Number
- This was good initially but when the loop names were updated in SPI, the import
would over-write the loop names (accessory tags for valve)

OILCO Import (Package 1), P ID

OILCO Import (Package 1), P ID

First, for the new tags

Second, for existing tags

28
Tips and Tricks for the Import

 Tags that are imported needed to have more than what the
import module had created
- Created an Access database and extracted the information from
SPI and P&ID system
- Compared and validated the tags at a tag level to all confirm the
information was transferred.
- The report compared the information on a tag basis
 The System Comparison was done based on entity
numbers but the import module used tag number for the
import
- Issues arose when there was a re-named tag
- The work-process had to entail the re-named tag at the P&ID
system and not directly in SPI

29
Conclusion

30
Conclusions

 AMEC used Oracle transfer with the SPI Import Module to transfer data
from P&ID system.

 It alleviated a lot of the EXCEL import problems and was a smooth

transfer, Excel was not a viable choice.

 AMEC used reports to validate the data that was transferred. Can use
SSRS, SQL Reporting (third party reporting tools as needed) to highlight
inconsistencies and post any reports with other tools for reporting.

 Oracle/SQL transfer is a viable method to incorporate third party data to

Intergraph SPI Import Utility to enhance data integrity and security.

31
Q&A