Built by Abdusalam Sungurov with Codex

One file.
Eight formats.
No uploads.

Electron turns incompatible oilfield chronology files into telemetry, events, settings, calculations, and engineering insight — entirely on the user's computer.

14isolated modules
8chronology formats
≈4 MBportable product
100%offline runtime
An anonymized Electron telemetry view with frequency, motor load, and voltage charts
Real product screenAnonymized demonstration data. No customer chronology or well identifier is included.
The problem

Field data should not depend on a server.

Control-station vendors store chronologies in different formats, while field computers may have no internet connection, no installation rights, or no original viewer. Electron provides one portable entry point without moving operational data off the machine.

01 / ROUTE

Detect the format

Drop in an ARH, OJN, JRN, ZQL, ELR, LOG, ZBK, or IRZ chronology. Electron identifies it and launches the correct viewer.

02 / UNDERSTAND

Turn records into insight

Explore synchronized telemetry charts, event journals, settings, operating periods, calculations, and technical references.

03 / PROTECT

Keep data local

The finished product is a self-contained HTML file. It needs no installation, CDN, account, analytics, upload, or cloud processing.

Real interface

Explore what was actually built.

Every image below is an anonymized screen from Electron v1.0. Choose a view to move through the product.

Electron home screen
One entry pointChronologies, calculators, formulas, and engineering references in one offline shell.
Human + Codex

Domain expertise became a maintainable product.

Electron was created through an iterative collaboration. The author defined the real engineering problem and product boundaries; Codex helped turn fourteen independent tools into one tested application.

Abdusalam Sungurov · Author

Oilfield knowledge, product ownership, operating constraints, and the final standard of correctness.

  • Defined the user workflow and supported station formats
  • Protected calculation logic and operational confidentiality
  • Supplied real-world edge cases and performed hands-on acceptance tests
  • Chose the portable, offline-only delivery model

Codex · Engineering partner

Architecture, implementation support, debugging, validation, documentation, and release preparation.

  • Audited fourteen standalone HTML tools and their dependencies
  • Designed lazy module isolation with embedded iframe.srcdoc
  • Adapted internal routing without rewriting domain algorithms
  • Built reproducible checks, privacy safeguards, documentation, and GitHub delivery
The result: one portable product that preserves fourteen specialist tools without forcing them into one fragile runtime.
Architecture

Isolation made consolidation possible.

Directly merging the tools would create collisions between CSS, element IDs, globals, and parser code. Electron instead embeds each module and starts it only when needed inside a fresh isolated document.

Electron.htmlOne portable product opened locally in Chrome
File routerDetects the chronology format and motor type
Isolated viewerLazy iframe.srcdoc prevents collisions
ParserVendor-specific binary and text interpretation
Engineering viewTelemetry, events, settings, charts, and export
Privacy by architecture

Operational files stay where they belong.

Electron does not promise privacy through a policy page. Its distributed build has no runtime network dependency, so chronology processing happens on the user's own computer.

Designed for disconnected field use

Copy one HTML file to a Windows computer, open it in Chrome, and select a chronology. No installer, server, account, or network connection is required.

No customer chronologies published
No well identifiers in public media
No CDN, analytics, or remote fonts
Separate private regression fixtures
Electron v1.0

Built from a real field need — and made possible with Codex.

Created by Abdusalam Sungurov (Sun6-6-6) in collaboration with Codex. Product decisions and oilfield expertise came from the author; Codex supported engineering, testing, documentation, and release.