Entry authorizations issued for Nanushuk road, pads; BRPC has Mustang Road issues

Kristen Nelson

Petroleum News

The Alaska Division of Oil and Gas has issued entry authorizations to Oil Search Alaska for pad and road work on its Nanushuk development at the Pikka unit on the North Slope. An entry authorization, EA, is a step in obtaining an easement, which is issued after terms and conditions of the EA have been met and construction and survey activities are complete.

Two of Oil Search’s easement applications, for its operations pad and production pad, drew no comments, but its application to extend and expand the Mustang Road to accommodate the Nanushuk project drew heated comments from Southern Miluveach unit operator Brooks Range Petroleum Corp., which built the Mustang Road for the development at the Mustang field, which began production late last year.

PIKKA solves everyday issues and makes life fuller, richer, tastier. It speaks a simple language: one that intrigues and interacts. All objects are clean in.

  • Alternatives to Pikka for Windows, Mac, Linux, Web, iPhone and more. Filter by license to discover only free or Open Source alternatives. This list contains a total of 25+ apps similar to Pikka. List updated: 10:36:00 AM.
  • January 23 2021, 18:00 GMT / 13:00 EST / 12:00 CST / 11:00 MT / 10:00 PST Greetings PikaCrafters, We are here to announce, what we believe, is a much-needed reset for survival.

Nanushuk access road

Oil Search, operator of the Pikka unit, applied for an easement to construct the Nanushuk access road in June, including making improvements to 4.3 miles of the existing Mustang Road and 0.4 miles of the existing Gravel Pit Access Road, as well as constructing new road infrastructure. Improvements include an expansion of the existing road base width and addition of high-quality material to improve load capacity.

The new segments include the 9.1-mile Nanushuk Access Road, the 0.1-mile ND-A Infield Road, the 3.2-mile ND-C Infield Road and the 0.1-mile water source access road and pump house pad.

The division said total proposed easement length for the road is some 17.8 miles.

“Based on the facts in the record and the Division’s knowledge of oil and gas construction activities, the Division concludes the Mustang Road easement is compatible with OSA’s proposed Road construction, operation, and maintenance activities and will not unreasonably interfere with BRPC’s development and production activities,” the decision says.

BRPC comments

BRPC made extensive comments on the OSA road easement application, basically arguing that it had a prior easement.

Among other things, BRPC told the state it spent more than $15 million on the Mustang Road to support its operations in the Southern Miluveach unit. On that issue the division said it was its understanding that the Alaska Industrial Development and Export Authority contributed some $20 million to the road with the current working interest owners contributing $10 million toward a total road cost of $30 million.

BRPC said it had contacted Oil Search about a commercial agreement “covering OSA’s proposed use of BRPC’s easement roadbed, and lands in the SMU. But to date, OSA has not meaningfully engaged with BRPC to resolve the issues … arising from the conflict between BRPC’s existing easement and improvements and OSA’s application.”

The division said it encouraged BRPC and OSA to reach agreement for compatible use of the road by both parties “but does not consider it necessary to condition OSA’s use on first entering into an agreement with BRPC.”

The division noted that the BRPC’s Mustang Road easement is a private non-exclusive easement in which the state “reserved the right to grant overlapping easements.”

BRPC argued that the division “cannot authorize a use that would unreasonably interfere with the use of a prior easement.” The division said OSA’s plan for the road “will improve the use of the road for both parties and is a compatible use that would not unreasonably interfere with current operation activities by BRPC.”

There is a 20-calendar day window for appeal.

Pad entry authorizations

OSA applied for a private exclusive easement for the Nanushuk Operations Pad, which will support operations with facilities including a 200-bed operations camp, office, warehouse, maintenance buildings, warm and cold storage buildings, wastewater treatment plants and temporary waste storage areas, communications structures, diesel-fired standby power generators and a helicopter landing pad. The operations pad will also house a diesel and gasoline tank farm.

The construction area for the pad is 21.8 acres and the estimated operational area is 20.3 acres.

The entry authorization, dated Jan. 3, has a term of 5 years; the easement will have a term of 35 years. The easement will be issued once terms and conditions of the EA are met.

Pikka

A $1 million bond is required to partially cover DR&R cost of the road, operations pad and facilities pad, and on or before May 30 OSA is required to deliver to DNR a DR&R cost estimate completed by a third-party engineering firm agreed to by DNR, with the remainder of the bond before Sept. 30 that equals 100% of the DR&R cost estimate.

There is a separate private exclusive easement application for the Nanushuk Processing Facility, which will house processing and utility modules for three-phase separation, heating and cooling, pumping, gas treatment and compression for gas lift and injection and water treatment for injection. The facilities pad will also house metering and pigging facilities, power generation facilities, a truck fill station, construction material and equipment staging area, a central control room, an equipment receiving module and a communications tower. The construction area for the facility pad is 21.4 acres; the estimated operational area is 20.7 acres.

This EA also has a term of 5 years; the easement will have a term of 35 years and will be issued once terms and conditions of the EA are met.


Did you find this article interesting?
Tweet it
Digg it

Click here to subscribe to Petroleum News for as low as $89 per year.

Push technology, or server push, is a style of Internet-based communication where the request for a given transaction is initiated by the publisher or central server. It is contrasted with pull/get, where the request for the transmission of information is initiated by the receiver or client.

Push services are often based on information preferences expressed in advance. This is called a publish/subscribe model. A client 'subscribes' to various information 'channels' provided by a server; whenever new content is available on one of those channels, the server pushes that information out to the client.

Push is sometimes emulated with a polling technique, particularly under circumstances where a real push is not possible, such as sites with security policies that require rejection of incoming HTTP/S requests.

General use[edit]

Synchronous conferencing and instant messaging are typical examples of push services. Chat messages and sometimes files are pushed to the user as soon as they are received by the messaging service. Both decentralised peer-to-peer programs (such as WASTE) and centralised programs (such as IRC or XMPP) allow pushing files, which means the sender initiates the data transfer rather than the recipient.

Email may also be a push system: SMTP is a push protocol (see Push e-mail). However, the last step—from mail server to desktop computer—typically uses a pull protocol like POP3 or IMAP. Modern e-mail clients make this step seem instantaneous by repeatedly polling the mail server, frequently checking it for new mail. The IMAP protocol includes the IDLE command, which allows the server to tell the client when new messages arrive. The original BlackBerry was the first popular example of push-email in a wireless context.[citation needed]

Another example is the PointCast Network, which was widely covered in the 1990s. It delivered news and stock market data as a screensaver. Both Netscape and Microsoft integrated push technology through the Channel Definition Format (CDF) into their software at the height of the browser wars, but it was never very popular. CDF faded away and was removed from the browsers of the time, replaced in the 2000s with RSS (a pull system.)

Other uses of push-enabled web applications include software updates distribution ('push updates'), market data distribution (stock tickers), online chat/messaging systems (webchat), auctions, online betting and gaming, sport results, monitoring consoles, and sensor network monitoring.

Examples[edit]

Webpush[edit]

The Webpush proposal of the Internet Engineering Task Force is a simple protocol using HTTP version 2 to deliver realtime events, such as incoming calls or messages, which can be delivered (or “pushed”) in a timely fashion. The protocol consolidates all real-time events into a single session which ensures more efficient use of network and radio resources. A single service consolidates all events, distributing those events to applications as they arrive. This requires just one session, avoiding duplicated overhead costs.[1]

Web Notifications are part of W3C standard and defines an API for end-user notifications. A notification allows alerting the user outside the context of a web page of an occurrence, such as the delivery of email.[2] As part of this standard Push API defined by W3C, is now being implemented by Chrome, Firefox, Edge, and Safari.[3]

HTTP server push[edit]

HTTP server push (also known as HTTP streaming) is a mechanism for sending unsolicited (asynchronous) data from a web server to a web browser. HTTP server push can be achieved through any of several mechanisms.

Pikka

As a part of HTML5 the WebSocket API allows a web server and client to communicate over a full-duplex TCP connection.

Generally the web server does not terminate a connection after response data has been served to a client. The web server leaves the connection open so that if an event occurs (for example, a change in internal data which needs to be reported to one or multiple clients), it can be sent out immediately; otherwise, the event would have to be queued until the client's next request is received. Most web servers offer this functionality via CGI (e.g., Non-Parsed Headers scripts on Apache HTTP Server). The underlying mechanism for this approach is chunked transfer encoding.

Another mechanism is related to a special MIME type called multipart/x-mixed-replace, which was introduced by Netscape in 1995. Web browsers interpret this as a document that changes whenever the server pushes a new version to the client.[4] It is still supported by Firefox, Opera, and Safari today, but it is ignored by Internet Explorer[5] and is only partially supported by Google Chrome.[6] It can be applied to HTML documents, and also for streaming images in webcam applications.

The WHATWG Web Applications 1.0 proposal[7] includes a mechanism to push content to the client. On September 1, 2006, the Opera web browser implemented this new experimental system in a feature called 'Server-Sent Events'.[8][9] It is now being standardized as part of HTML5.[10]

Pushlet[edit]

In this technique, the server takes advantage of persistent HTTP connections, leaving the response perpetually 'open' (i.e., the server never terminates the response), effectively fooling the browser to remain in 'loading' mode after the initial page load could be considered complete. The server then periodically sends snippets of JavaScript to update the content of the page, thereby achieving push capability. By using this technique, the client doesn't need Java applets or other plug-ins in order to keep an open connection to the server; the client is automatically notified about new events, pushed by the server.[11][12] One serious drawback to this method, however, is the lack of control the server has over the browser timing out; a page refresh is always necessary if a timeout occurs on the browser end.

Long polling[edit]

Long polling is itself not a true push; long polling is a variation of the traditional polling technique, but it allows emulating a push mechanism under circumstances where a real push is not possible, such as sites with security policies that require rejection of incoming HTTP/S Requests.

With long polling, the client requests information from the server exactly as in normal polling, but with the expectation the server may not respond immediately. If the server has no new information for the client when the poll is received, instead of sending an empty response, the server holds the request open and waits for response information to become available. Once it does have new information, the server immediately sends an HTTP/S response to the client, completing the open HTTP/S Request. Upon receipt of the server response, the client often immediately issues another server request. In this way the usual response latency (the time between when the information first becomes available at the next client request) otherwise associated with polling clients is eliminated.[13]

For example, BOSH is a popular, long-lived HTTP technique used as a long-polling alternative to a continuous TCP connection when such a connection is difficult or impossible to employ directly (e.g., in a web browser);[14] it is also an underlying technology in the XMPP, which Apple uses for its iCloud push support.

Flash XMLSocket relays[edit]

Pikka 2 0 12

This technique, used by chat applications, makes use of the XMLSocket object in a single-pixel Adobe Flash movie. Under the control of JavaScript, the client establishes a TCP connection to a unidirectional relay on the server. The relay server does not read anything from this socket; instead it immediately sends the client a unique identifier. Next, the client makes an HTTP request to the web server, including with it this identifier. The web application can then push messages addressed to the client to a local interface of the relay server, which relays them over the Flash socket. The advantage of this approach is that it appreciates the natural read-write asymmetry that is typical of many web applications, including chat, and as a consequence it offers high efficiency. Since it does not accept data on outgoing sockets, the relay server does not need to poll outgoing TCP connections at all, making it possible to hold open tens of thousands of concurrent connections. In this model, the limit to scale is the TCP stack of the underlying server operating system.

Reliable Group Data Delivery (RGDD)[edit]

In services such as Cloud Computing, to increase reliability and availability of data, it is usually pushed (replicated) to several machines. For example, the Hadoop Distributed File System (HDFS) makes 2 extra copies of any object stored. RGDD focuses on efficiently casting an object from one location to many while saving bandwidth by sending minimal number of copies (only one in the best case) of the object over any link across the network. For example, Datacast [15] is a scheme for delivery to many nodes inside datacenters that relies on regular and structured topologies and DCCast [16] is a similar approach for delivery across datacenters.

Push notification[edit]

A push notification is a message that is 'pushed' from backend server or application to user interface, e.g. (but not limited to) mobile applications[17] and desktop applications. Push notifications were first introduced by Apple in 2009.[18][dubious]In 2010 Google released its own service, Google Cloud to Device Messaging. (It has since been replaced by Google Cloud Messaging and then Firebase Cloud Messaging.)[19]November 2015, Microsoft announced that the Windows Notification Service would be expanded to make use of the Universal Windows Platform architecture, allowing for push data to be sent to Windows 10, Windows 10 Mobile, Xbox, as well as other supported platforms using universal API calls and POST requests.[20]

Push notifications are mainly divided into 2 approaches, local notifications and remote notifications.[21] For local notifications, the application schedules the notification with the local device's OS, or, alternatively, sets as a timer in the application itself if it is able to continuously run in the background. When the event's scheduled time is reached, or the event's programmed condition is met, the message is displayed in the application's user interface.

Remote notifications are handled by a remote server. Under this scenario, the client application needs to be registered on the server with a unique key (e.g., a UUID). The server then fires the message against the unique key to deliver the message to the client application via an agreed client/server protocol such as HTTP or XMPP and the client displays the message received. When the push notification arrives, it can transmit short notifications and messages, set badges on application icons, blink or continuously light up the notification LED, or play alert sounds to attract user's attention.[22] Push notifications are usually used by applications to bring information to users' attention. The content of the messages can be classified in the following example categories:

  • Chat messages, e.g.: messages from Facebook messenger sent by other users.[23]
  • Vendor special offers, e.g.: A vendor may want to advertise their social offers to the customers.
  • Event reminder, e.g.: Some application may allow the customer to create reminder or alert for a specific time.
  • Subscribed topics changes, e.g.: Users may want to get updates regarding the weather in their location, or monitor a web page to track changes, for instance.

Real-time push notifications may raise privacy issues since they can be used to bind virtual identities of social network pseudonyms to the real identities of the smartphone owners.[24]

See also[edit]

References[edit]

  1. ^M. Thomson, E. Damaggio and B. Raymor (October 22, 2016). 'Generic Event Delivery Using HTTP Push'. Internet Draft. Internet Engineering Task Force. Retrieved October 28, 2016.
  2. ^'Web Notifications'.
  3. ^'Web Push API'.
  4. ^CGI Programming on the World Wide Web O'Reilly book explaining how to use Netscape server-push
  5. ^Server-Push Documents (HTML & XHTML: The Definitive Guide)Archived 2008-04-17 at the Wayback Machine O'Reilly book explaining server-push
  6. ^Remove support for multipart/x-mixed-replace main resources
  7. ^'Web Applications 1.0 specification'.
  8. ^'Event Streaming to Web Browsers'. 2006-09-01. Retrieved 2007-03-23.
  9. ^'Opera takes the lead with AJAX support among browsers: More efficient streaming'. 2006-09-01. Archived from the original on 2007-03-18. Retrieved 2007-03-23.
  10. ^Server-Sent Events
  11. ^Pushlets introduction
  12. ^Van Den Broecke, Just (1 March 2000). 'Pushlets: Send events from servlets to DHTML client browsers'. JavaWorld. Retrieved 2020-07-13.
  13. ^'RFC6202 - Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP'. Retrieved 2016-05-14.
  14. ^'XEP-0124: Bidirectional-streams Over Synchronous HTTP (BOSH)'. Retrieved 2012-06-26.
  15. ^C. Guo; et al. (November 1, 2012). 'Datacast: A Scalable and Efficient Reliable Group Data Delivery Service For Data Centers'. Microsoft Research. ACM. Retrieved Jun 6, 2017.
  16. ^M. Noormohammadpour; et al. (July 10, 2017). 'DCCast: Efficient Point to Multipoint Transfers Across Datacenters'. USENIX. Retrieved Jun 6, 2017.
  17. ^Wohllebe, Atilla. (2020). 'Consumer Acceptance of App Push Notifications: Systematic Review on the Influence of Frequency'. International Journal of Interactive Mobile Technologies. 14 (13): 36–47. doi:10.3991/ijim.v14i13.14563.
  18. ^'iPhone push notification service for devs announced'. Engadget. Retrieved 2016-10-18.
  19. ^'Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework'. InfoQ. Retrieved 2016-10-18.
  20. ^mijacobs. 'Windows Push Notification Services (WNS) overview'. docs.microsoft.com. Retrieved 2017-10-20.
  21. ^'Local and Remote Notifications in Depth'. developer.apple.com. Retrieved 2016-10-18.
  22. ^'Android and iOS Push Notifications – Blog – JatApp'. jatapp.com. Retrieved 2017-10-20.
  23. ^'How do I adjust my mobile push notifications from Facebook? Facebook Help Center Facebook'. www.facebook.com. Retrieved 2016-10-18.
  24. ^Loreti, Pierpaolo; Bracciale, Lorenzo; Caponi, Alberto (2018). 'Push Attack: Binding Virtual and Real Identities Using Mobile Push Notifications'. Future Internet. 10 (2): 13. doi:10.3390/fi10020013.

External links[edit]

Pikka 2 0 12 0

  • W3C Push Workshop. A 1997 workshop that discussed push technology and some early examples thereof
  • HTTP Streaming with Ajax A description of HTTP Streaming from the Ajax Patterns website
  • The WebSocket API candidate recommendation
  • HTML5 Server-Sent Events draft specification

Game 2.0

Retrieved from 'https://en.wikipedia.org/w/index.php?title=Push_technology&oldid=1006339089'
⇐ ⇐ Workspaces 1 5 2 0
⇒ ⇒ Librarian Pro 3 0 6 – Complete Personal Inventory System