DOMAIN PLANT AREA UNIT HIERARCHY CONSIDERATIONS BY: DENNIS COOLEY

Size: px

Start display at page:

Download "DOMAIN PLANT AREA UNIT HIERARCHY CONSIDERATIONS BY: DENNIS COOLEY"

Luke Andrews
5 years ago
Views:

1 DOMAIN PLANT AREA UNIT HIERARCHY CONSIDERATIONS BY: DENNIS COOLEY

2 HIERARCHY EXAMPLE 2

3 SEED Data Sharing For Each Option Separate Database Instance One Instance One Instance One Domain One Instance One Domain One Plant Separate Separate Separate Domain Plant Unit Domain Sharing/Aligned (Out Of The Box OOTB) Instrument Datasheet Forms N N Y Y Instrument Types N N Y Y Standard Pick-lists e.g. I/O Types, Manufacturers, Model Numbers N N Y Y Plant Sharing/Aligned User Defined Fields (UDF) N N N Y User Defined Tables (UDT) N N N Y Line Numbers, Equipment Names, P&ID drawing names N N N Y 3

4 COMPARISON HIGHLIGHTS I.T. Administrator Work For Each Option Separate Database Instance One Instance One Instance One Domain One Instance One Domain One Plant Separate Separate Separate Domain Plant Unit I.T. / SPI Administrator Work Requires new Database (Instance) Y N N N Requires new Domain (Schema) Y Y N N Requires new Plant Y Y Y N Requires new Area Y Y Y Maybe Requires new Unit Y Y Y Y Manually create Naming Conventions (versus copying a Naming Convention) Y Y N N Deliverable archive configuration (Archive or not to Archive) Y Y Y- in Owner Operator mode N Requires new user groups Y N Maybe Maybe Requires more involved access rights to protect each stakeholders data N Maybe Y Y Requires new user accounts to be created and managed Y N Maybe Maybe Requires new Database Platform Y - if on different version N N N Requires independent Server Hardware Y - if on different version N N N Requires new Citrix Deployment setup Y N N N Legend Y = more work for Administrator; configuration setup, and maintenance N = less work for Administrator; configuration setup, and maintenance Maybe - is situation dependent. 4

5 Business Benefits For Each Option Separate Database Instance One Instance One Instance One Domain One Instance One Domain One Plant Separate Separate Separate Domain Plant Unit Business Benefits Performance Y - #1 Y - #2 Y - #3 Y - #1 Security Y - #1 Y - #2 Y - #3 Common Autonomy to Upgrade Y - #1 Y - #2 Y - #3 Common Autonomy of Project, EPC Y - #1 Y - #2 Y - #3 Common Enables new Symbols, Templates, Title Blocks e.g. Enhanced Reporting Tool Y - #1 Y - #2 Common Common Report compilation ease (compiling information to report) Y - #4 Y - #3 Y - #2 Y - #1 Domain sharing/alignment is possible (OOTB) N N Y Y - #1 Plant sharing/alignment is possible (OOTB) N N N Y - #1 Legend Y - #1 = Best Y - #2 = Better Y - #3 = Good Y - #4 = Advanced effort is required Common - is common for all options 5

6 Discussion Openers / Reasons for a Separate Database Separate Facility - not related to others Separate Facility could/will be sold off separate from other assets Separate Control System, separate Wiring Panels Separate Tagging - totally independent of others Security - concerns; who can access data at backend Well Pad Template Design being offered by EPC to Owner Operator Admin. activities impacting database availability e.g. Merging & Claiming General concerns - high risk of corruption due to certain activities by others; must reduce risk 6

7 Discussion Openers / Reasons for One Database Integration with SPF requires one Database and one Plant Future Domain, Plant, Area, Unit duplication requirements Better, easier management of Tags, deliverables/revision management Easier to compile information into reports SPI Support Team (staffing levels, available skill sets, cost) Integration with other Design Tools, Procurement Systems Integration with Data Warehouse e.g. SPF 7

8 All Things Considered It May Come Down To These Reasons Integration alignment with other applications e.g. SPF Corporate Culture Corporate Direction Owner Operator Project Manager influence Information Management Team / SPI Manager/ SPI Lead influence SPI Operators, Maintenance expertise EPC capabilities - SPI experienced, well trained designers Corporate Maturity SPI related SPI related work processes (Excellent, Good, Fair, Bad, Does Not Exist) Standards (Excellent, Good, Fair, Bad, Does Not Exist) SPI Administrative Support (Excellent, Good, Fair, Bad, Does Not Exist) SPI As-Building internal capabilities & work processes 8

9 9

10 Thanks! 10

11 MATERIAL TO ADD SOMEWHERE Having separate plants (for different facilities still shares one As-Built section). Having separate Domains requires software solutions and diligence to keep the standards e.g. datasheets, Spec data dictionaries, instrument types aligned. 11

BLENDING SPI DATABASES. Presented by: CooleyCore Feb. 13, 2018

BLENDING SPI DATABASES. Presented by: CooleyCore Feb. 13, 2018 BLENDING SPI DATABASES Presented by: CooleyCore Feb. 13, 2018 COOLEYCORE PROFILE HIGHLIGHTS Incorporated: January, 2008 Head Office: Calgary, Canada Products: software applications and services Industries: