DoE LPG systems enhancement · Abu Dhabi · 2023–2025
A multi-year program to enhance LPG detection and control systems across Abu Dhabi. Delivery involved multiple sites and parties, with field checks, progress records, and acceptance documentation that needed to stay connected.
I supported project coordination and field execution, and developed documentation tools using Excel and Python. The aim was a repeatable path from site observations to documents that engineers could review.
01 — The approach
The work had two closely related parts: coordinating the activities around the installation, and giving the resulting information a consistent structure.
In the field
Commissioning activities were organized around the gas control panels and associated safety systems.
The purpose was to make site readiness and the next required action easier to establish.
In the data
I developed internal tools to carry field and project information into repeatable document layouts.
Generated documents still required engineering review and the applicable acceptance process.
02 — Documentation automation
Excel supplied the structured records. Python checked and transformed the inputs, filled the templates, and recorded the outcome of each run.
Capture progress, inspection details, and the relevant reference fields in a consistent worksheet structure.
Check required information, status consistency, and template placeholders. Flag entries or mappings that need correction.
Use the spreadsheet fields to fill predefined report and certificate layouts, keeping repeated formatting work in the templates.
Produce documents in batches and record processing results. Review the output and resolve exceptions before the documents enter the acceptance process.
Automation supports the review. A generated document records the supplied information. Its technical content, required evidence, and approval still need to be checked by the responsible people.
03 — Progress integrity
Different parties needed to understand the same site status. I used explicit progress states and named the outstanding conditions, so a partial activity could be discussed without presenting it as accepted work.
Started
An activity has begun. Its remaining tasks and dependencies are still part of the progress record.
Partial
Some prerequisites or tasks are complete. Record the outstanding condition and attach a next action.
Complete
The applicable completion criteria have been met, with the required evidence and acceptance recorded.
A useful status explains what is stopping the next activity and who needs to act. That gives coordination meetings a specific issue to resolve.
Maintain the execution record while the work is underway. Close-out can then focus on checking the available evidence and resolving gaps.
04 — Lessons carried forward
Agree what each state means and what evidence supports it. Use those definitions consistently across the field team and project reviews.
Identify the missing condition, the next step, and the responsible party. Visibility is useful when someone can act on it.
Reusable layouts and structured inputs make recurring documents easier to produce and inspect.
Use software to reduce repeated data entry and expose exceptions. Keep engineering judgment, inspections, and authorized acceptance within the workflow.