Fracture network simulations Sample Clauses

Fracture network simulations. The simulations followed the onsite stimulation procedure and indicate a fracture growth and coalescence of pre-existing fractures from the Muschelkalk/PCT upwards to the injection borehole. The fracture growth depends on the pressure conditions within the borehole, i.e., fractures propagate and coalescence in case fluid is injected while the fractures remain stable under in-situ conditions. During the first phase, no additional mechanical load or hydraulic pressure is applied on the borehole walls. During that phase, the whole geomechanical system is stable and the fractures do not propagate, independent of the formation (Figure 24A). Applying a pressure of 46 MPa during the second phase on the borehole wall leads to fracture propagation within the Muschelkalk while cracks within the other formations show no propagation (Figure 24B). Once the fractures in the Muschelkalk have propagated, they become unstable, so that in the third phase, where the pressure in the borehole is reduced to zero, they commence to propagate until they reach the borders to the surrounding layers (Xxxx/Dogger and PCT). The PCT is not penetrated by the fractures, since the crack propagation stops shortly before and the Xxxx Formation/Dogger boundary is penetrated before the propagation ends (Figure 24C). In the fourth phase, the pressure in the borehole is increased again, which leads to a fracture growth into the PCT (Figure 24D). By reaching the PCT the pore pressure that was restricted by the Muschelkalk spreads out into the Xxxx Formation /Dogger along the newly created fracture pathway. In the fifth phase, the pressure in the borehole is decreased to zero, however, the fracture propagate upwards and with it the pore pressure until they reach the borehole (Figure 24E and F). The propagation and coalescence of the fracture lead to a fracture network that connects the over-pressured PCT with the remaining formations. At this point the gas kicks in, visible in a higher pore pressure at the borehole. The outcome of these simulations supports the likelihood of a connection from the PCT to the well, as suggested by Xxxxxxxx et al. (2015). Furthermore, the simulations present a pathway for a fluid/pressure transport from the well to the reservoir and vice versa underlining the high probability of seismicity that was induced by the well control measures instead of a poroelastic stress transfer. <.. image(Ein Bild, das xxxxxxx enthält. Automatisch generierte Beschreibung) removed ..>
AutoNDA by SimpleDocs

Related to Fracture network simulations

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Network Congestion Reduced Speed for Routing or Answering 911 Dialing Calls. There may be a greater possibility of network congestion and/or reduced speed in the routing of a 911 Dialing call made utilizing the Service as compared to traditional 911 dialing over traditional public telephone networks.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

  • Network Connectivity Farmington Area Public Schools makes no guarantee that their network will be up and running 100% of the time. In the rare case that the network is down, the District will not be responsible for lost or missing data. Attribution 4*

  • SS7 Network Interconnection 9.7.1 SS7 Network Interconnection is the interconnection of Global Connection local signaling transfer point switches or Global Connection local or tandem switching systems with BellSouth signaling transfer point switches. This interconnection provides connectivity that enables the exchange of SS7 messages among BellSouth switching systems and databases, Global Connection local or tandem switching systems, and other third-party switching systems directly connected to the XxxxXxxxx XX0 network.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

Time is Money Join Law Insider Premium to draft better contracts faster.