PRODML Network Models

1
PRODML Network Models

• Stan DeVries

2
Network Modeling IT Scope
Network Model
External data transfer
Data Processing / monitoring and reporting
software
AP 3
AP x
AP 4
AP 5
AP 2
AP 1



Office Domain
Application Databases
Historian

DCS and real time applications
real time apps
DCS historian

Process Control Domain
Fields instruments
3
How a Network Model Helps

• Supports ProdML objectives of plug and play and
  network-based modeling of data
• Will allow each application to consume its
  desired granularity of information about the
  model
• Allows users to feasibly implement a range of
  production optimization scopes
• Report only needs flows
• Equipment optimization needs full equipment
  detail
• Field-wide optimization needs selective detail

4
The 4 Key Concepts

• Use a meta-object facility (MOF) recommend W3C
  WSMO (web services modeling ontology)
• Use the ProdML 1.0 for the data layer of the MOF
• Combine Concepts 1 and 2 to produce an XML file
  of the Network Model
• Extend the Network Model for simulation parameters

5
Concept 1 Web Services Modeling

• Use a part of an ambitious program
• Use the modeling language (WSML) to define
  relationships
• Layers for
• Information (ProdML 1.0)
• Model (metadata that links information)
• Meta-Model (structure and semantics)

6
How Concept 1 Helps

• The Network Model can be distributed
• The richness of a model can vary with its need
  mix detailed equipment models with less granular
  asset flow models
• Sub models are decoupled and can evolve
  independently

7
Concept 2 WITSML/ProdML

• Flow Network
• Collection of connected Flow Units.
• Product Flow Model
• Collection of Flow Networks
• Product Volume Report
• Measurements of p,v,t,q, in fluid flows.
• Production Operations Report
• Activities related to production.

8
Flow Network

• Represents a flow system.
• Named collection of connected Units.
• A unit is a black box that describes the flow
  into or out of something.
• Flow properties can be measured at a Port.
• A network may have external ports.

9
Flow Network Flow Unit

• A black box with ports but an internal network
  allows drill-down for more details.
• A unit can represent
• A complex thing like a platform or separator.
• A simple thing like a valve or choke.
• Contextual knowledge (i.e., what does this unit
  represent).

10
Flow Network Flow Port

• Represents a real world measurement point on a
  facility.
• Has an expected direction (inlet or outlet).
• Connects to one Node - may represent a
  many-to-many connection.
• May have an expected Product Flow (for validation
  purposes) e.g., oil production or gas
  injection.
• Future - Control point (across two ports)

11
Flow Network Port Direction

• The direction is the intended direction of flow.
• A change in pressure across a unit can change the
  actual flow direction at a port.
• In the Product Volume Report
• A positive volume represents an intended
  direction (i.e., a flow out of an outlet port or
  into an inlet port).
• A negative volume represents an unintended
  direction (i.e., a flow into an outlet port and
  out of an inlet port).

B3
12
Expected Product Flow

• Pairs of product kind and flow kind where
• Product oil, gas, condensate, aqueous, oleic,
  vapour, water, carbon dioxide gas, etc.
• Flow production, injection, consume, import,
  export, gas lift, overboard, etc.

13
Node (artificial concept)

• All ports that are connected to the same node are
  connected to each other.
• For an actual flow diagram the graphics may
  ignore the node.

14
Flow Assumptions

• Steady state fluid flow across nodes and ports.
  That is, pressure is constant across internally
  and externally connected ports and nodes.
• Conservation of mass across a node or port.
• The temperature and other properties can vary
  between connected ports.
• Pressure can vary internally between ports on a
  unit.

15
Internal Network of a Unit

• Corresponding ports have the same name (i.e.,
  they are logically the same port).
• There is no pressure change across ports or
  nodes. Thus, there is no pressure change between
  ports A2 and C1.

16
Flow Network What good is it?

• Defines the connectivity status of one fluid
  system over time. That is, how fluid could
  flow.
• Defines measurement points within the fluid
  system.
• The flow connectivity is independent of physical
  descriptions.
• The connectivity can be tailored to specific
  business scenarios.
• Requires something else to capture actual flow
  properties over time.

17
Exercise - Start
18
Exercise - Measurements
19
Exercise - Boundary
20
Exercise - Hide
21
Exercise End
22
Concept 3 Linked Models

• A production reporting scope can have a single
  model, or integrate portions of detailed models
• Integrated models can share details
• Models are linked with metadata and a modeling
  language

Flow Model
Gathering System Model
Facilities Model
Injection System Model
Compressor Model 1
Compressor Model 2
Well Model 1
Well Model 2
23
Concept 4

• Extend the ProdML model to include shared
  simulation data
• Example pipe diameter, length, elevation
• Increase robustness and accuracy of architectures
  that use multiple models
• Well
• Solids
• Gathering
• Facilities
• Equipment (e.g. compressors)

24
Proposal

• Use the n-port modeling from ProdML 1.0
• Use a portion of W3C Modeling (compliant but not
  conformant)
• Implement an approach to help applications
  discover changes in the Network Model (no
  automation or proactive behavior is implied)
• Support parallel and diverse evolution of
  equipment, flow and facility models