Enterprise Internal Tool
Preventive Maintenance Report Builder
Web application concept for managing preventive maintenance schedules, asset tracking, report generation, reminder automation, and loaned asset management.
Role
Product Engineer
Duration
Internal workflow improvement
Author
Jason Sariwating
Overview
This case study focuses on designing an internal tool to reduce manual work in preventive maintenance reporting. The system centralizes schedules, assets, report data, reminders, and loaned asset tracking into a structured workflow.
Background
Preventive maintenance workflows often depend on spreadsheets, manual reminders, repeated document formatting, and scattered asset records. This makes reporting slower and creates room for inconsistent data.
Problem
- Maintenance schedules were difficult to track consistently.
- Report generation required repeated manual formatting.
- Asset and loaned equipment information could become fragmented.
- Follow-up reminders depended heavily on manual coordination.
Solution
The proposed solution is a web application that combines asset records, preventive maintenance schedules, report generation, and reminders in one workflow. The goal is to make operational status easier to review and reduce repetitive administrative work.
Architecture
User
Web Application
Backend API
Database
Report Generator
Notification Layer
My Contribution
- Role: Product Engineer.
- Responsibilities: solution design, workflow mapping, UI planning, backend workflow design, reporting logic, testing scenarios, and technical documentation.
- Technologies used: React, backend API, database, automation, reporting workflow.
Challenges
- Designing a workflow that supports real operational habits.
- Keeping asset data structured without making the UI heavy.
- Building report output that remains consistent and easy to review.
- Balancing automation with manual review steps.
Impact
- Clearer preventive maintenance workflow.
- Reduced repetitive report preparation.
- Better visibility into asset and loaned equipment status.
- Easier follow-up and operational tracking.
Lessons Learned
Internal tools work best when they match the real workflow closely. The engineering challenge is not only building forms and tables, but reducing friction while keeping the data reliable.