HSE Observation & Reporting Application

Delivery Details

Developed in Petro Infotech.

A focused project snapshot with client context, delivered scope, and petroleum safety visuals aligned as one case-study block.

Major Client: Petroleum Development Oman

Location: Muscat, Oman
Project Scope: HSE observation, reporting, review, and closure workflow.
Responsibilities: Application development, project coordination, UI design, software design, and database architecture participation.

Field observation in petroleum operationsCapture observations before unsafe actions become incidents.

Refinery and process safety awarenessChecklist groups reveal recurring risk patterns.

Immediate action for urgent observationsSubmit high-risk items directly to HSE review.

Technology Stack

Enterprise Microsoft stack with web reporting.

The application was developed with C#, .Net, WCF, SQL Server 2012, RDLC Reporting Services, ASMX, Bootstrap, HTML, CSS, and JavaScript.

C# / .Net

Core application development for the web solution.

WCF / .Net / ASMX

Service communication and legacy integration endpoints.

SQL Server

Database architecture and observation data storage.

RDLC Reports

Graphs and reports for HSE analysis and corrective action.

Application Purpose

Designed to reduce incidents through early observation and intervention.

HSE Reporting System is an intuitive application for logging, managing, and automating HSE observations and reports. Its main objective is to eliminate incidents and injuries by observing people, identifying unsafe actions, and helping HSE teams intervene quickly.

✓Capture safety observations, checklist items, comments, and immediate actions from the field.

✓Submit observations to the HSE department for review, escalation, and corrective action.

✓Analyze stop cards and recurring safety issues by PPE, behaviors, tools, and equipment categories.

Observation Lifecycle

From field observation to HSE corrective action.

The workflow promotes safe behavior as part of the health and safety management system.

Observe

Observer or observer group identifies activity conditions in the work area.

Capture

Checklist groups such as PPE, behaviors, tools, and equipment are marked with comments.

Submit

Safety observation is sent to the HSE department, including urgent immediate-action notes.

Act

HSE teams review violations, take informed action, and prevent incidents before injuries occur.

Modules Handled

Everything required to run HSE observations from user setup to reports.

The system includes administration, observation capture, and reporting tools for a complete safety management workflow.

01

User Registration

Admin users can register, edit, and delete users while adjusting solution-wide settings for the HSE application.

02

Safety Observation Form

Observers record working-area observations, checklist results, comments, unsafe actions, and urgent immediate actions.

03

Reports & Graphs

RDLC-based reporting turns submitted stop cards into clear trend analysis for informed prevention decisions.

Administrative control for users and settings.

The admin module manages user access and the entire solution configuration, giving the HSE department control over how observations are captured and routed.

Register, edit, or delete users
Adjust application settings
Maintain controlled access for observers and HSE reviewers

Core safety observation capture.

Observers can mention working-area observations, mark checklist items, add comments, and submit the record for further HSE action.

Safety observation form for individuals or groups
Standard checklist groups for fast analysis
Immediate action field for urgent situations

Department review and corrective action.

Once submitted, the HSE department can review the violation, identify major safety issues, and act before unsafe behavior becomes an incident.

Track submitted observations
Prioritize high-risk unsafe actions
Use trend data to prevent future injuries

Observation Review

Turn field observations into safer operating decisions.

Submitted observations help HSE teams identify unsafe patterns, review recurring risks, and assign practical actions before small warning signs become serious events.

Observation records become prevention signals.

For petroleum operations, useful observation data should show where the unsafe condition was found, what immediate action was taken, which team owns the follow-up, and whether the control reduced the risk.

CategorizeGroup observations by PPE, behavior, tools, equipment, working area, and unsafe condition.

ReviewCheck submitted comments, images, checklist results, and immediate-action notes.

PreventUse recurring trends to prioritize corrective actions and toolbox-talk topics.

Immediate Notification Alert HSE, area supervisor, maintenance, and emergency response teams based on severity, location, and asset category.

Scene Control & Evidence Record initial photographs, witness statements, equipment tag numbers, permits, and temporary controls before conditions change.

Root-Cause Investigation Look past the direct trigger and identify procedural, training, equipment, supervision, and management-system contributors.

Management Review Review serious incidents with accountable owners, due dates, residual risk assessment, and lessons learned for affected teams.

Immediate Remedy System

Contain the hazard now, then fix the system that allowed it.

Immediate remedy is the first layer of protection: stop work, isolate the hazard, make the area safe, and document what was done. Corrective action is the second layer: remove the underlying cause so the event does not repeat.

Severity Routing

Select a severity to preview the remedy path.

Low Severity

RemedyCorrect at source

SLASame shift

EvidencePhoto + observer note

Medium Severity

RemedySupervisor review

SLA24-48 hours

EvidenceAction owner + verification

High Severity

RemedyStop work / isolate

SLAImmediate escalation

EvidenceHSE approval before restart

1

Make Safe

Stop unsafe activity, isolate energy or equipment, barricade the area, and provide first response if needed.

2

Notify

Route alerts to HSE, line supervisor, maintenance, and emergency contacts according to risk level.

3

Assign

Create a corrective-action ticket with responsible owner, due date, priority, and expected evidence.

4

Verify

Close only after evidence is reviewed and the HSE team confirms the control is effective.

Action Tracking & CAPA

Every recommendation needs an owner, deadline, evidence, and closure decision.

OSHA PSM requires systems to promptly resolve incident findings and recommendations, document corrective actions, and communicate relevant actions to affected employees. This page now reflects that same control mindset for the application.

Action Item Owner Priority Status

Replace damaged scaffold tag and inspect access ladder Area Supervisor High Open

Update PPE checklist for hot work observation form HSE Admin Medium Verified

Conduct toolbox talk on dropped-object prevention Permit Coordinator Medium In Progress

Attach before/after evidence for barricade correction Maintenance Lead High Due Today