We built a unified data platform over 14 weeks. Data ingestion layer (weeks 1-5): connecting 14 source systems. Real-time connectors: building data connectors for each source system — drilling management (custom API connector — the system providing REST APIs for daily report data), well services (database connector — direct read from the Oracle database), equipment fleet (IoT connector — GPS and telematics data from equipment via MQTT), HSE (web scraping connector — the legacy HSE system lacking APIs, requiring automated data extraction from the web interface), SAP (standard OData connector for financial and HR data), and sensor data (OPC-UA connector for wellsite sensor data — pressure, temperature, flow, and vibration).
Batch connectors: for systems with limited real-time capability — Excel-based systems (2 legacy systems still producing Excel reports — automated ingestion with validation), email-based data (some field reports arriving as structured emails — automated parsing and ingestion), and client portal data (reverse integration — pulling data from ADNOC portals for reconciliation). Data pipeline: Kafka (deployed in Azure UAE North) as the real-time streaming backbone — all source system data flowing through Kafka topics, enabling: real-time processing for operational dashboards, event-driven alerts for safety and maintenance triggers, and replay capability for reprocessing historical data. Data transformation layer (weeks 3-8): unified data model.
Common data model: designing a unified data model across all 14 systems — well master (a single definition of each well, linking drilling, completion, production, and service data), equipment master (unified equipment record linking fleet tracking, maintenance, certification, and utilisation data), employee master (unified employee record linking HR, competency, safety training, and project assignment), and project master (unified project record linking operational data, financial data, and client deliverables). Data quality: automated quality checks on every data element — completeness (required fields present), validity (values within expected ranges), consistency (cross-system reconciliation — equipment GPS location matching assigned project location), and timeliness (data arriving within expected latency — real-time data within 30 seconds, batch data within defined windows).
Arabic data handling: field reports and HSE observations containing Arabic text — Arabic NLP processing for: incident classification (automatically classifying Arabic safety observations into categories), name matching (matching Arabic employee names across systems with different transliteration conventions), and document extraction (extracting structured data from Arabic PDF reports). Analytical layer (weeks 6-12): insight delivery. Operational dashboards: real-time dashboards showing: well status (current operations at each of 120 well sites — drilling progress, service status, production metrics), equipment fleet (location, utilisation, maintenance status for every piece of equipment — real-time GPS tracking and telematics), HSE performance (incident trends, observation rates, near-miss reporting — updated in real-time as field observations are submitted), and financial performance (project profitability, revenue by client, cost tracking — updated daily from SAP).
ADNOC reporting automation: daily drilling reports automatically compiled from source data — formatted per ADNOC requirements and generated by 04:00 (2 hours ahead of the 06:00 deadline, allowing time for human review before submission). Monthly HSE reports: automatically aggregated from the unified data platform — generated on the 1st business day of each month (previously taking 3-5 days). Predictive maintenance: machine learning model trained on historical equipment data — predicting equipment failures 72 hours before occurrence, enabling planned maintenance rather than emergency response. The model: ingesting sensor data (vibration, temperature, pressure), maintenance history, operating hours, and environmental conditions (Abu Dhabi's extreme heat affecting equipment differently than temperate climates). Equipment optimisation: utilisation analytics identifying: underutilised equipment (available but not scheduled — visibility enabling better scheduling), maintenance timing optimisation (scheduling maintenance during planned downtime rather than disrupting operations), and fleet right-sizing (data-driven analysis of whether the fleet size matches operational demand).