Internal Operations System
SKK
Internal operations platform for SKK Migas — budget visibility (including SAKTI pagu), official travel, procurement, and payments in one workspace.
Project Overview
SHINTA (Sistem Informasi Terpadu) is the internal operations platform for SKK Migas. It brings budget monitoring, official travel (perjadin), procurement, and payments into one authenticated workspace so operators can follow structured processes instead of scattered tools. Dashboards compare SAKTI budget ceiling and realization with SHINTA's own allocation, then drill into travel requests, procurement packages, and payment status. As a Frontend Developer at Grasiapp.id, I implemented the application UI across sign-in, executive dashboards, and the four core modules so the interface stays consistent for day-to-day SKK Migas operators.
- Client
- SKK Migas
- Company
- Grasiapp.id
- Platform
- Web Application
- Duration
- 2024 – Present
- Frontend
- Next.js, React
- Backend
- Laravel
- Database
- PostgreSQL
- Deployment
- Docker + VPS
Features
Fiscal-year login
Authenticated sign-in with year selection so operators work inside the correct anggaran period.
Executive summary
Cross-module overview of budget, travel, procurement, and payment health for operators.
SAKTI vs SHINTA budget
Side-by-side ceiling and realization views for SAKTI pagu and SHINTA allocation.
Official travel (Perjadin)
SPD workflows from application through execution and declaration with attachments and approvers.
Procurement pipeline
Package monitoring across submission, review, selection, contract, payment, and completion stages.
Payment tracking
Visibility into invoice and disbursement status across SPP, SPM, and SP2D-style process steps.
Reference data
Shared referensi surfaces that keep forms and dashboards aligned across modules.
Role-aware operator UI
Consistent sidebar navigation and role-bound screens for day-to-day SKK Migas operators.
Gallery
Timeline
01 · Discovery
Mapped SKK Migas operator needs across anggaran, perjadin, pengadaan, and pembayaran.
02 · Planning
Scoped module IA, fiscal-year auth, and a delivery sequence for the four core domains.
03 · Design
Established shared shells, status patterns, and dashboard cards for dense operational data.
04 · Development
Built Next.js/React UI for sign-in, executive views, and module workflows on Laravel APIs.
05 · Testing
Validated multi-step forms, dashboard filters, and role-aware navigation with operators.
06 · Deployment
Shipped to Docker/VPS hosting and continued iterative UI improvements in production.
Challenges & solutions
Challenge
Two budget sources
Operators needed SAKTI pagu/realization and SHINTA allocation visible without mixing the two systems.
Challenge
Multi-stage workflows
Perjadin (three stages) and pengadaan (eight stages) had to stay scannable while capturing dense form data.
Challenge
Data-heavy screens
Executive and procurement views pack KPIs, charts, pipelines, and tables that can overwhelm non-technical staff.
Solution
Shared UI patterns
Reusable page shells, sidebars, filters, and form layouts kept all four modules coherent.
Solution
Status cards and pipelines
Stage steppers, deadline badges, and summary cards make process health readable at a glance.
Solution
Fiscal-year-bound auth
Login year selection anchors every module to the correct anggaran period from the first screen.
Tech
Outcomes
4 modules
Anggaran, Perjadin, Pengadaan, Pembayaran
SAKTI
Pagu visibility alongside SHINTA
1 hub
Unified SKK Migas operations workspace
2024–
In production
More work
Want something similar?
Tell me about the product, the users, and the constraint that matters most.
Let's talk