Professional Documents
Culture Documents
Architecture Review R2B
Architecture Review R2B
• The project is divided into six packages to include engineering State-owned Petroleos Mexicanos
and construction work: (Pemex) will be the owner and
• 27 processing plants or Units
operator of the refinery
• Power plants
• 93 storage tank and spheres
• A new pipeline will connect to maritime terminal
Confidential Property of Schneider Electric | Page 2
Internal
1.2.2 Site Information
Package I Package IV
1.7 B US 0.3 BUS
•Distillation Plant • Sulphur recovery plant
•Coking plant • Gas recovery and treatment plant
• Hydrogen-producing plant
• Columna C3 Splitter
Package Package V
Asociados Constructores DBMR II - III
0.4 B US
• Storage facilities
1.7 B US
•
•
Diesel hydro desulphurisation (DHDT) Unit
gasoil hydro desulphurisation (HDS) Unit Package VI
• Naphtha hydro-treating (NHT) Unit
• Naphtha reformer Unit
1.8 B US
• Refinery integration services.
1.4 B US
•Fluid catalytic cracking (FCC)
• The systems to be provided are: 3A ICAF -UOP 209 Planta Isomerizadora de Butanos 3
210 3
• DCS Planta de Alquilación
212 Unidad de Tratamiento de Aguas Amargas 6
• ESD 213 Unidad Regeneradora de Amina 6
• FGS 4A Techint 401 y 402 Suministro y Pretratamiento de Agua 8
• SINE (Sistema Integral de Notificación de Emergencias)= 418 Planta Tratamiento de Efluentes 7
Emergency notification system connected to the FGS. 420 Almacenamiento y Recibo de Sosa Caustica 7
211 5
• SIAD (Sistema de Información y Administración de Planta de Tratamiento de Gases
214 Planta Recuperadora de Azufre 6
Datos)= PI OsiSoft? 4B ICAF
215 Planta de Hidrógeno 4
• AVEVA OTS 412 Desfogue 6
• AVEVA OMM & TIS & DBS, Blending package 305 Báculas de Carrotanques y Autotanques
• Networks are independent between sectors. They only converge 308 Sistema de Drenajes Aceitoso, Químico, Sanitario y Pluvia 7
(Cárcamos)
to the top level through firewalls for the SIAD and the SINE 405 Torres de Agua de Enfriamiento (Equipos Auxiliares)
systems. 406 Recuperación y Tratamiento de Condensado 8
• Each sector will have dedicated 407 Sistema de Combate Contraincendio NA
• redundant domain controller, 454 Casas de Bombas 7
410 7
• galaxy, 6 PROYECTA
Sistema Mezclado en Línea
411 Patines de Regulación y Medición 7
• historian and 419 Almacenamiento y Distribución de Nitrógeno 8
• redundant of data collectors. 423 Red de Aire de Instrumentos y Aire de Planta 8
• One centralized control room. 424 Suministro de Gas Combustible 8
426 Sistema de Azufre Líquido
428 Instrumentación Área de Almacenamiento 7
430 Acueducto 8
Confidential Property of Schneider Electric | Page 5 431 Gasoducto
Internal SN JADIAZ 317 Cuarto de Control Central
1.1.1 Scope of Work by systems and plants
453 EFFLUENTS (WASTE), STORAGE AND RECEIPT OF SULFURIC ACID AND CAUSTIC SODA X X X X
454 STORAGE AND MOVEMENT OF PRODUCTS X X X X X X
Sector 6 Sector 2
Sector 7 Sector 3
• There are eight sectors, each one of them, provides information to the higher hierarchy data networks.
• SIAD the administration network gets the information through an AIM OPC data server (non-redundant) in each sector
• SINE the emergency notification system gets the information through a Triconex P2P coms with the FGS (redundant)
UNIT 201
• Six FCP280
• Four FDC280
• Thirteen Tricon CXs for ESD/BMS
• Three Tricon CXs for FGS
• Five V91
• One H90
• I/O:
• 4.2K DCS
• 1.9K ESD/BMS
• 1.3K FGS
UNIT 202
• Six FCP280
• Four FDC280
• Thirteen Tricon CXs for ESD/BMS
• Three Tricon CXs for FGS
• Five V91
• One H90
• I/O:
• 4.2K DCS
• 1.9K ESD/BMS
• 1.3K FGS
UNIT 405
• 2 FCP280
• 2 FDC280
• I/O:
• 100 DCS
• 2.2K Soft
UNIT 418 UNIT 420 UNIT 409A UNIT 410 UNIT 428
• 3 FCP280 • 2 FCP280 • 2 FCP280 • 2 FCP280 • 2 FCP280
• 3 FDC280 • 4 FDC280 • 4 FDC280 • 4 FDC280 • 4 FDC280
• 2 Tricon CXs for ESD • 2 Tricon CXs for ESD • 2 Tricon CXs for ESD • 2 Tricon CXs for ESD • 2 Tricon CXs for ESD
• 1 Tricon CXs for FGS • 1 Tricon CXs for FGS • 1 Tricon CXs for FGS • 1 Tricon CXs for FGS • 1 Tricon CXs for FGS
• 5 V91 • 1 H90 • 1 H90 • 1 H90 • 1 H90
• 1 H90
• 10 Thin clients
UNIT 412
• 1 FCP280
• 2 FDC280
• 1 Tricon CXs for FGS
• 1 H90
• I/O:
• 160 DCS
• 96 FGS
• 700 Soft
Pending information, waiting for the PO, part of this sector will be done in Italy, out of the Mexico Office Scope.
V91 Virtual Server 1 (V914R4440LA0 6 VM) V91 Virtual Server 2 (V914R4440LA0 6 VM)
Slot NAME Role NAME Role
HDD (GB)
HDD (GB)
(C: & D:)
(C: & D:)
Memory
Memory
CPU
CPU
(GB)
(GB)
(#)
(#)
V91-01-CCC- V91 Licensed for 6 VMs 20 304 3050 V91-01-CCC- V91 Licensed for 6 VMs 18 296 2700
01 02
1 CVM102 SDC CVM 2 8 200 OW2013 Estación de Operación 2 16 200
2 OW2011 Estación de Operación 2 16 200 OW2014 Estación de Operación 2 16 200
3 OW2012 Estación de Operación 2 16 200 SIF101 SIF Manager (PSA OP Core) 2 8 250
4 SIF104 SIF Manager (Console) 2 8 150 SIF102 SIF Manager (Historian) 2 8 300
5 Available --- --- --- --- SIF103 SIF Manager (Collector) 2 8 150
6 Available --- --- --- --- Available --- --- --- ---
7 OW2013' Estación de Operación 2 16 200 OW2011' Estación de Operación 2 16 200
8 OW2014' Estación de Operación 2 16 200 OW2012' Estación de Operación 2 16 200
9 --- --- --- --- --- --- --- ---
10 --- --- --- --- --- --- --- ---
11 --- --- --- --- --- --- --- ---
12 --- --- --- --- --- --- --- ---
13 --- --- --- --- --- --- --- ---
14 --- --- --- --- --- --- --- ---
Number of core (8/16) 16 --- --- Number of core (8/16) 16 --- ---
Hyper threading (y/n) yes --- --- Hyper threading (y/n) yes --- ---
CAPACITY 32 384 4200 CAPACITY 32 384 4200
TOTAL usage in Virtual Machines 12 80 1150 TOTAL usage in Virtual Machines 14 88 1500
Host Machine snapshot required HDD space --- --- 287.5 Host Machine snapshot required HDD space --- --- 375
(25% of each VHDD) (25% of each VHDD)
Minimum for Host OS 6 77 --- Minimum for Host OS 6 77 ---
AVAILABLE 14 227.2 2762.5 AVAILABLE 12 219.2 2325
V91 Virtual Server 3 (V914V4440LA0 14 VM) V91 Virtual Server 4 (V914V4440LA0 14 VM)
NAME Role NAME Role
HDD (GB)
HDD (GB)
(C: & D:)
Memory
(GB)
CPU
(GB)
(#)
(#)
V91-01-CCC- V91 Licensed for 14 VMs 16 320 2350 V91-01-CCC- V91 Licensed for 14 VMs 14 312 2200
03 04
EWS101 Galaxy Repository / Estación de Ingeniería 4 16 550 HSS101 Servidor Histórico 4 16 700
DCS101 Colector de Datos Principal 2 8 200 DCS102 Colector de Datos Secundario 2 8 200
SDC101 SDC offmesh.local 2 8 200 PDC101 PDC offmesh.local 2 8 200
Available --- --- --- --- EPO101 McAfee ePO 2 8 150
Available --- --- --- --- Available --- --- --- ---
Available --- --- --- --- Available --- --- --- ---
Available --- --- --- --- Available --- --- --- ---
Available --- --- --- --- Available --- --- --- ---
SIF101' SIF Manager (PSA OP Core) 2 8 250 MW0101' Maintenance Advisor 4 16 200
SIF102' SIF Manager (Historian) 2 8 300 SA0101' System Advisor 4 16 200
SIF103' SIF Manager (Collector) 2 8 150 DCS101' Colector de Datos Principal 2 8 200
DCS102' Colector de Datos Secundario 2 8 200 SIF104' SIF Manager (Console) 2 8 150
--- --- --- --- --- --- --- ---
--- --- --- --- --- --- --- ---
Number of core (8/16) 16 --- --- Number of core (8/16) 16 --- ---
Hyper threading (y/n) yes --- --- Hyper threading (y/n) yes --- ---
CAPACITY 32 384 4200 CAPACITY 32 384 4200
TOTAL usage in Virtual Machines 16 64 1850 TOTAL usage in Virtual Machines 22 88 2000
Host Machine snapshot required HDD space --- --- 462.5 Host Machine snapshot required HDD space --- --- 500
(25% of each VHDD) (25% of each VHDD)
Minimum for Host OS 6 77 --- Minimum for Host OS 6 77 ---
AVAILABLE 10 243.2 1887.5 AVAILABLE 4 219.2 1700
HDD (GB)
(C: & D:)
Memory
CPU
(GB)
(#)
V91-01-CCC- V91 Licensed for 14 VMs 10 296 2050
05
CVM101 PDC CVM 2 8 200
MW0101 Maintenance Advisor 4 16 200
SA0101 System Advisor 4 16 200
CMC101 Consola de Administración Central 2 8 150
MRC101 MRC Domain Controller 2 8 150
Available --- --- --- ---
Available --- --- --- ---
Available --- --- --- ---
EWS101' Galaxy Repository / Estación de Ingeniería 4 16 550
HSS101' Servidor Histórico 4 16 700
--- --- --- ---
--- --- --- ---
--- --- --- ---
--- --- --- ---
Number of core (8/16) 16 --- ---
Hyper threading (y/n) yes --- ---
CAPACITY 32 384 4200
TOTAL usage in Virtual Machines 22 88 2150
Host Machine snapshot required HDD space --- --- 537.5
(25% of each VHDD)
Minimum for Host OS 6 77 ---
AVAILABLE 4 219.2 1512.5
Data collectors:
As you can see in the architectures, there are a pair of data collectors per sector, and we are planning to create dedicated VMs in order to fulfill
this functionality. One Historian VM Server per sector.
Message manager:
Planning to use MM mode, we need to pick two stations to receive the alarms…
Do we need to have a dedicated VMs for this functionality?
Is it ok to select operator VMs?
What about replicating them?
Operator workstations:
Should we replicate the VM for the operators and put them in different V91, so we lose one of them at a time when we need to
patch the Host server.
1. we discussed to put this VM on the mesh or leave it off mesh. What is recommended? The benefits are time synchronization
and System manager monitoring but the cons are harder to maintain, loss of resources, performance impact, multiple networks,
etc.
2. Should we replicate the VM of the Historian server? Since Data Collectors are redundant, they should be able to store the data
until the Historian server VM is back.
The installation manual does not recommend to install the Domain for the replication in the Foxboro domain controller, but since
they are 8 independent sectors this will mean we will need 32 VMs for domain controller functionality, 16 for the corporate (8
primary and 8 secondary) + 16 CVM (8 PDC and 8 SDC). If we can validate the consolidation of the domains this will be reduced to
16 (two per sector).
6.3.3. Consolidation of Domains
The consolidation of Domains is not currently an accepted design for Foxboro DCS, ACN, and VHN, it could be part of a future
DCS product scope and eventually involve cost savings in having just one Domain for the overall CVM architecture.
VLANs:
We are sharing switches between different networks. This will require to create different VLANs and somehow segregate ports in
the switches for the different networks…
How should we prioritize the different networks?
Switch configuration software alone won’t work…
Should we keep the MESH network isolated from the others?
ESD & FGS networks?
MESH and ACN are sharing the switches. VHN and Backup network are shared.
AIM OPC server or FS Gateway?
VLANs:
There is an OPC server per sector to provide information to the SIAD, (corporate information network) most likely to be PI:
Our proposal was to provide AIM OPC server but thinking in the lifecycle of the product:
We are almost in the position to start installing the systems… but we were told that CS 7.3 is coming out by the end of the month, to
avoid rework can we get an early release of the software, or we should just wait to the formal release
There is an idea to add Excel and Visio to the operator workstations… Visio for the live view functionality… Excel for the Query the
Aveva Historian. Do you think we should give the operators this kind of access? Or should be only for the engineer stations?
1) P2P networks for the ESD, there is one Triconex in the CCR, with a P2P network, sending the CCR pushbuttons to the Triconex’
s for each units.
2) P2P network for the FGS system, all the FGS Triconex send information by P2P network to the centralized Triconex for the SINE
system.
• BorderGuard
• Guardian