Case study
KSS Reporting System with Laravel
Operations, Maintenance, and HSE reports now follow one flow, from a draft in the field to an archive that can be traced back.
- Context
- Internship 2025 — Undergraduate thesis 2026
- Focus
- Requirements analysis, development, and testing
- Stack
System screens
Sample data
It started with the shift change
During my internship, I built a shift-report app for the Operations Division. Maintenance and HSE still kept their records semi-manually. Some reports took one to three days to reach the manager, and information between crews was easy to miss.
Three stages of development
I observed the work in the field and interviewed users before planning three stages of work.
- Cleaning up Operations reports, access rights, and archives.
- Adding daily Maintenance reports.
- Bringing HSE reports into the same approval flow.
Decisions inside the interface
- The Operations form is split into eight steps. Crew leaders can save a draft and continue once the data is complete.
- Night-shift dates follow the time the shift starts. Every handover shows the sending and receiving crews.
- Managers review and sign reports across divisions. Admins manage users and archives. Separating access protects the approval process.
Test results
All 105 black-box test scenarios passed. In an acceptance test based on ISO/IEC 25010, 13 active users gave the system a score of 93.22%. The system is used for daily reporting at PT Kaltim Satria Samudera.
Project demo
A crew leader logs operational activity. When the shift changes, both crews sign the handover. Reports can be exported to PDF or Excel.





