Documente Academic
Documente Profesional
Documente Cultură
Agenda
Introduction
− BIO
− AMEC
− This data migration was Independent and external source /third party
software to import directly into the SPI Import Utility
2
Introduction
3
Introduction
Once, tag and loop data was imported, other EXCEL imports were
used to transfer the data, i.e. UDF fields
4
Configuration and
Coordination
5
Configuration and Coordination
P&ID SPI
Data Data
Instrument
Type
Views
Entity SPI Import Module
Number
6
Configuration and Coordination
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
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.
8
Configuration and Coordination
Once the Oracle Views were created, the SPI Import Module can use the view
as a Table Import.
9
Configuration and Coordination
Used existing import links that were created for the import.
10
Configuration and Coordination
Instrument Type
& Description
P&ID - P&ID
Equipment Description
Name
Line Number
Line Size/Unit
11
Configuration and Coordination
Tag Name
Loop Name
12
Oracle Views and
SPI Import Module
13
Oracle Views and SPI Import Module
- 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)
- 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
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.
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 :
20
Comparison Reports for Validation
21
Comparison Reports for Validation
22
Comparison Reports for Validation
Line
Number
23
Comparison Reports for Validation
P&ID
24
Comparison Reports for Validation
P&ID
25
Comparison Reports for Validation
P&ID
P&ID Tags
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)
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.
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.
31
Q&A