System study & flowcharts
Mapped incident capture, immediate remedy, root-cause analysis, and action closure into a workable workflow before screens were built.
Recruiter case study
Incident Management, Action Tracking & Immediate Remedy
I was a major developer on this petroleum incident platform at Petro Infotech. It helps operations record incidents, apply immediate remedy, investigate root cause, and track every HSE action until closure.
Who I was
Major developer on the delivery team
What we built
Incident-to-remedy control loop
Who used it
Field teams and HSE reviewers
Core platform
Microsoft enterprise web stack
Output
RCA, LTI rates, closed actions
01 / My contribution
What I owned as a major developer.
Recruiters should read this first: I was not a peripheral contributor. I worked across system study, software design, database architecture, responsive UI, RDLC reporting, and module development for this incident platform.
Software design
Shaped module boundaries, service contracts, and review routing so an event could move from report to investigation without leaving the system.
Database architecture
Designed SQL Server 2008 structures for incident records, evidence metadata, action ownership, and HSE reporting data.
UI and module development
Built field-friendly incident entry, review screens, and action tracker views with Bootstrap, HTML, CSS, and JavaScript.
RDLC reporting support
Supported dashboards, graphs, and calculated HSE rates — including LTI, AFR, AIR, and ASR — so management could see incident performance, not just individual cases. This is the role to remember: a major developer who could design the workflow, build the product, and keep reporting honest.
02 / The project
A centralized system for petroleum incident control.
When an incident happens, operations need one place to record it, limit disruption, store evidence, and prove that remedy and follow-up actually closed.
The problem
Incident details lived in paper copies, delayed emails, and disconnected files. That made evidence easy to lose, root cause harder to find, and corrective actions easy to forget.
The product
A web system for recording incidents, attaching photos and policy files, applying immediate remedy, running post-incident analysis, and tracking HSE actions until closure.
Why it matters
The goal is control, then learning: capture the event quickly, reduce active risk, investigate failed barriers, and close actions with ownership so the same incident does not repeat.
Incident desk
Open cases, remedy, and rates
New incident
Open incidents
24
Actions closed
61
High severity
07
Process leak — Train 2
High
Vehicle near-miss — Gate 4
Open
Dropped object — Workshop
Closed
INCIDENT FORM
Report the event
Working area
Offshore deck — West
Severity
High — injury potential
Immediate remedy
Isolate area, notify supervisor
Evidence
deck-west.jpg attached
Report
Capture the incident, area, severity, people involved, documents, and photographs.
Contain
Make the record available quickly so operations can control risk and limit disruption.
Remedy
Log urgent corrective measures and temporary controls before final investigation.
Investigate
Run root-cause analysis, identify failed barriers, and define prevention actions.
Learn
Capture post-incident lessons so handling methods improve and repeats are reduced.
Close
Assign actions to people or departments, track progress, and close with accountability.
03 / Systems and Features of Application
Incident control, analysis, and action closure.
A focused HSE incident suite for petroleum operations — recording events, storing evidence, calculating safety rates, and keeping corrective work visible until it is done.
Authorized personnel record incidents from any location, attach documents and photos, and keep every accident or near-miss in one system.
Structured records replace paper copying errors, so root cause, failed controls, and prevention measures stay attached to the case.
Actions from incidents, observations, audits, or reviews are assigned with ownership, tracking, and closure discipline.
This centralized web system records incidents, controls operational disruption, stores evidence, analyses post-incident learning, and tracks HSE actions until closure across petroleum operations.
Incident information is available only to authorized personnel. The platform was designed to link with observation, audit, and related HSE applications so follow-up work is not stranded in a separate spreadsheet.
Reporting covers export, import, dashboards, graphs, and calculated HSE rates including LTI, AFR, AIR, and ASR — giving management a rate view, not just a list of cases.
Application features
Incident reporting
Capture event details, affected area, severity, people involved, policy references, and photographs from the field.
Evidence storage
Supporting documents, policy files, and images stay with the incident record instead of circulating as unmanaged copies.
Immediate remedy
Record quick corrective measures and temporary controls to reduce active risk before final closure.
Root cause analysis
Identify underlying causes, failed controls, and prevention measures against the original event.
Post-incident learning
Capture lessons to prevent repeat incidents and refine response methods across sites.
HSE rate reports
Automatic LTI, AFR, AIR, and ASR calculations for confident management and regulatory reporting.
Action tracking
Track assigned actions by person, department, source, and status until verified closure.
Secure access
Incident information is restricted to authorized personnel, with role-based review and closure rights.
HSE integration
Designed to link with observation, audit, and incident applications so actions share one tracker.
Systems of the application
System 01
Incident Register
Single source for event records, evidence, policy files, and images so every accident or near-miss has one reliable home.
Authorized personnel can capture incident details from any location and keep the case history attached as investigation proceeds.
- Event, area, severity, and people involved in one record
- Supporting documents and photographs stored with the case
- Policy references linked instead of copied by hand
- Searchable history for authorized HSE and operations users
- Status visible from first report through final closure
04 / Technology stack
Enterprise Microsoft stack with web reporting.
The system was developed with WCF, C#, ASP.NET, SQL Server 2008, RDLC Reporting Service, Bootstrap, HTML, CSS, and JavaScript. This is the stack I used on the project.
Presentation
What users touch
Bootstrap
HTML
CSS
JavaScript
Application
Business logic
C#
ASP.NET
Services
Integration
WCF
Data
Persistence
SQL Server 2008
Reporting
HSE insight
RDLC Reporting Service
WCF / C# / ASP.NET
Core application development, service communication, and business workflow implementation from report through closure.
SQL Server 2008
Database architecture for incident records, action ownership, evidence metadata, and reporting data.
RDLC + Bootstrap
RDLC for LTI, AFR, AIR, and ASR reports. Bootstrap, HTML, CSS, and JavaScript for field-friendly incident screens.
05 / Modules
The system I helped design and build.
Six areas cover the full loop: register the event, apply immediate remedy, investigate cause, learn from it, report rates, and close every action.
Incident register and evidence
This is the heart of the product. Authorized users log what happened, attach documents and photographs, and keep the case as the single source of truth.
- Event, location, severity, and people involved
- Policy files, photos, and supporting documents
- Restricted access for authorized personnel only
Open24
High07
Closed118
INC-2042 · Process leak
High
INC-2048 · Near-miss
Review
Immediate remedy controls
Before investigation finishes, the team records urgent corrective measures and temporary controls so active risk is reduced on the same shift.
- Quick corrective measures against the open incident
- Temporary controls and response notes
- Visible status while the full RCA is still running
Isolate Train 2 west line
Done
Barricade and notify supervisor
Done
Standby fire watch
In place
Root cause analysis
Investigate why the incident happened, identify failed barriers, and define prevention actions so the same event does not recur.
- Underlying causes and contributing factors
- Failed controls recorded against the case
- Prevention measures generated as tracked actions
Barrier: isolation certificate
Failed
Barrier: toolbox talk
Partial
Prevention: update PTW checklist
Action
Post-incident analysis
Learning capture after the event: what worked, what failed, and how response methods should change across sites.
- Lessons attached to the closed incident
- Improved handling methods for similar events
- Shared learning for operations and HSE teams
Lesson: isolation proof before start
Shared
Lesson: photo evidence on remedy
Draft
HSE reports and calculated rates
RDLC reports, dashboards, and graphs turn case data into LTI, AFR, AIR, and ASR figures for management review.
- Automatic LTI, AFR, AIR, and ASR calculations
- Export, import, dashboards, and graphs
- Trend visibility without paper re-keying
LTI0.12
AFR1.8
ASR24
Monthly rate pack
Export
Action tracker and ownership
Actions created from incidents, observations, audits, or reviews are assigned to people or departments with status tracking until verified closure.
- Ownership by person, department, source, and status
- Guided procedures from assignment through close-out
- Accountability instead of actions lost in email
Replace isolation tag
Due
Update PTW checklist
Owner: HSE
Toolbox talk — dropped objects
Closed