Government – Public Sector

BPKAD Kabupaten Tanah Laut

BPKAD managed official vehicles across multiple SKPDs with no centralized monitoring. Vehicle data was scattered across spreadsheets, and every administrative process required a physical cover letter signed by the Head of Department — creating recurring delays whenever the signatory was unavailable.

Metric

Digital vehicle administration platform serving all SKPDs in Kabupaten Tanah Laut

Result

Developed a centralized vehicle administration platform combining status monitoring, automatic cover letter generation, and Electronic Signature (TTE) integration with Kominfo — reducing manual process dependency and accelerating administrative services involving BPKAD, Ditlantas Polda Kalsel, and Samsat.

Highlights

Centralized vehicle registry as single source of truth
Automated administrative deadline monitoring
Automatic cover letter generation from stored data
TTE integration eliminating physical signature bottleneck
Digital document archive with full traceability
Real-time compliance reporting without manual recompilation

SIMPKB (Sistem Informasi Pajak Kendaraan Bermotor) is a centralized platform developed for BPKAD Kabupaten Tanah Laut to manage the end-to-end administration of official government vehicles — from monitoring tax and registration deadlines to generating cover letters signed electronically through Kominfo's TTE service.

More than a vehicle database, SIMPKB was designed to eliminate the two systemic bottlenecks that caused recurring administrative delays: fragmented vehicle data and dependency on physical document signatures.

The Problem

BPKAD Kabupaten Tanah Laut manages official vehicles distributed across multiple SKPDs. Every vehicle has periodic administrative obligations — tax payments, STNK renewal, ownership changes, and plate number updates.

Before SIMPKB, two systemic problems made this unmanageable.

Problem Discovery

Two Critical Bottlenecks

Before SIMPKB, BPKAD Kabupaten Tanah Laut managed official vehicles across multiple SKPDs. Each vehicle required periodic administrative tasks: tax payments, STNK renewal, ownership changes, and plate number updates. Two systemic problems made this unmanageable.

Lack of Administrative Visibility

Vehicle data and administrative status were scattered across documents and spreadsheets, making monitoring nearly impossible.

Consequences

  • Difficult to identify vehicles approaching deadlines
  • Monitoring performed manually across spreadsheets
  • High risk of administrative delays and penalties
  • Reporting required repeated manual recompilation

Document Issuance Bottleneck

Every administrative vehicle process required a physical cover letter signed by the Head of Department — creating a single point of failure.

Consequences

  • Documents printed physically and queued for signature
  • When the authorized signatory was absent, documents piled up
  • Administrative processes that should be routine became dependent on one person's physical presence
  • Delays cascaded to Ditlantas Polda Kalsel and Samsat

The Real Cost

These weren't just inefficiencies — they had cascading operational consequences. Vehicle tax deadlines were missed because no one could see them coming. Cover letters piled up on a desk waiting for one person's signature. Administrative work that should have been routine became unpredictable.

The core issue wasn't a lack of effort. It was a process design gap — the work was being done, but without structure, without visibility, and with a single point of failure at the signature stage.

Process Analysis

The transformation required understanding both the existing manual flow and the desired digital one.

Process Analysis

Before vs After

Manual & Reactive

Vehicle Data Collection

Spread across documents and spreadsheets

Spreadsheet Monitoring

Manual check of scattered records

Identify Admin Needs

Manually determine what's due

Draft Cover Letter

Create from scratch each time

Print Document

Physical printing required

Wait for Signature

Queue for Head of Department

Deliver to Samsat / Ditlantas

Physical document handover

Key Weak Spots

  • Vehicle monitoring is not centralized
  • Document issuance depends on manual process

The analysis revealed two weak spots that needed to be addressed:

  1. Vehicle monitoring was not centralized — data lived in scattered spreadsheets
  2. Document issuance depended on a manual process — physical printing and signing

Both issues caused recurring delays. The goal was to transform a manual, reactive process into an integrated, monitored, and digitized system.

System Architecture

SIMPKB was built as a centralized platform connecting vehicle data management with regional vehicle administration processes.

System Architecture

Core Components & High-Level Architecture

4 Components

SIMPKB is built as a centralized platform connecting vehicle data management with regional vehicle administration processes.

Vehicle Registry

Central data hub for all government official vehicles.

Administration Monitoring

Track tax status and vehicle administration deadlines.

Document Management

Automatically generate cover letters from vehicle data.

Electronic Signature

TTE integration through partnership with Kominfo.

High-Level Architecture

SKPD & BPKAD Users
SIMPKB Platform
Vehicle Database
TTE Kominfo API

The Architecture Decision

The platform connects four layers:

  • Vehicle Registry serves as the single source of truth for all government vehicle data
  • Administration Monitoring provides visibility into tax status and upcoming deadlines
  • Document Management generates cover letters automatically from stored vehicle data
  • Electronic Signature integrates with Kominfo's TTE API service for digital signing

The integration with Kominfo's TTE service was a critical architectural decision. Rather than building a proprietary signing mechanism, SIMPKB leverages the government's existing electronic signature infrastructure — ensuring legal validity and interoperability with other government systems.

Security Design

Given the sensitivity of vehicle data and the legal requirements for administrative documents, security was designed around four pillars:

  • Document validity — ensuring TTE-signed documents are legally recognized
  • Data integrity — preventing unauthorized modification of vehicle records
  • Access security — role-based access for BPKAD and SKPD users
  • Auditability — complete traceability of all system actions

Product Design

Product Design

Design Principles

5 Principles

SIMPKB was designed to simplify vehicle administration from start to finish, guided by five core principles.

Single Source of Truth

All vehicle information stored in one system — no more scattered spreadsheets.

Monitor Before Problems

Users see potential administrative issues before deadlines arrive.

Generate Once

Already-stored data is reused to produce administrative documents automatically.

Paperless Administration

Reduce dependency on physical documents through digital workflows.

Compliance-Oriented

Help ensure government vehicles meet all applicable administrative obligations.

These principles guided every design decision:

  • Single Source of Truth means no more wondering which spreadsheet has the latest data. All vehicle information lives in one place.
  • Monitor Before Problems shifts the team from reactive firefighting to proactive management. Deadlines are visible before they arrive.
  • Generate Once eliminates redundant data entry. Vehicle data entered once is reused across all administrative documents.
  • Paperless Administration reduces the dependency on physical documents that previously caused bottlenecks.
  • Compliance-Oriented ensures the system actively helps maintain regulatory compliance rather than just recording violations after they occur.

Workflow Automation

Workflow Automation

Five Automated Workflows

5 Stages

SIMPKB automates the full vehicle administration lifecycle — from monitoring to reporting.

Workflow 1

Centralized Monitoring

Vehicle administration status can be monitored from a single dashboard. No more checking spreadsheets across departments.

Workflow 2

Auto Document Generation

Cover letters are generated directly from stored vehicle data — eliminating manual drafting and reducing errors.

Workflow 3

Electronic Signing

Documents can be signed electronically through TTE integration, removing the dependency on physical signatures from specific officials.

Workflow 4

Digital Archive

Documents are stored digitally and can be traced back at any time — a complete, searchable administrative record.

Workflow 5

Reporting

Reports are generated directly from the system without manual recompilation, providing real-time status and compliance data.

Centralized Monitoring

Before SIMPKB, checking which vehicles were approaching tax deadlines meant opening multiple spreadsheets and mentally cross-referencing dates. With SIMPKB, the system surfaces this information automatically — showing at a glance which vehicles need attention, when, and for what reason.

Automatic Document Generation

Cover letters — previously drafted from scratch each time — are now generated directly from stored vehicle data. The system pulls the relevant vehicle details, populates the document template, and prepares it for signing. This eliminates both the manual drafting time and the risk of data entry errors.

Electronic Signing Workflow

This is where the biggest bottleneck was eliminated. Instead of printing documents and waiting for a physical signature, the document enters an electronic signing workflow through Kominfo's TTE service. The authorized official can sign from anywhere — no physical presence required. Once signed, the document is legally valid and ready for use by Samsat or Ditlantas.

Digital Archive

Every document — generated, signed, or uploaded — is stored digitally with full metadata. Need to find last year's cover letter for a specific vehicle? Search and retrieve in seconds, not hours of digging through physical files.

Reporting

Reports that previously required manual recompilation from spreadsheets are now generated directly from the system. Real-time status, compliance rates, and historical data are available on demand.

Software Engineering

Requirement Analysis

The project began with direct observation of BPKAD's vehicle management and administration processes. Understanding the actual workflow — not just the documented procedure — was essential to designing a system that would actually be adopted.

Business Process Mapping

The key insight came from mapping the business process: the bottleneck wasn't in any single step — it was in the transition between steps. The handoff from document drafting to signing, and from signed document to delivery, were where delays accumulated.

Domain Modeling

The system was designed around six core entities:

Vehicle → SKPD → Vehicle Administration → Cover Letter → User → Electronic Signature

Each entity maps to a real-world concept in the government's vehicle management workflow, making the system intuitive for users who understand the business domain even if they're not technically sophisticated.

API Integration

TTE integration required coordination with Kominfo to obtain technical documentation and access credentials. The integration layer was designed to handle the asynchronous nature of electronic signatures — a document can be sent for signing, and the system tracks its status until the signed version is returned.

Impact

Impact Measurement

Results & Outcomes

6 Outcomes

SIMPKB transformed how BPKAD manages vehicle administration — delivering measurable improvements across visibility, efficiency, and compliance.

 

Improved Visibility

Comprehensive overview of all official vehicle administrative status.

 

Faster Processing

Cover letter issuance time significantly reduced compared to previous manual process.

 

Reduced Bottlenecks

Dependency on physical signatures minimized through TTE integration.

 

Better Data Accuracy

Vehicle data stored centrally and easier to update — single source of truth.

 

Operational Efficiency

Monitoring, reporting, and document issuance handled in one platform.

 

Digital Transformation

Part of the broader government digitalization effort — moving from paper-based to digital processes.

For BPKAD

Complete Visibility — Leadership gained a comprehensive view of all official vehicle administrative status without asking for manual updates.

Accelerated Processing — Cover letter issuance time was significantly reduced. What previously took days of drafting, printing, and waiting for signatures now happens within the system.

Eliminated Signature Bottleneck — The dependency on physical signatures was minimized through TTE. Administrative processes no longer stall when specific officials are unavailable.

Better Governance — Centralized data, automated monitoring, and digital archiving improved data accuracy and accountability.

For SKPDs

Clear Status Tracking — Each vehicle's administrative status is visible — which documents are due, which are being processed, and which are complete.

Faster Turnaround — Cover letters are generated and signed faster, reducing the wait time for administrative processing with Samsat and Ditlantas.

For the Broader Ecosystem

Government Digital Transformation — SIMPKB represents a concrete step in digitizing government administration that was previously paper-based. It demonstrates how targeted software can eliminate process bottlenecks that affect multiple agencies (BPKAD, Ditlantas, Samsat).

Key Achievement

SIMPKB successfully combined vehicle status monitoring, automatic cover letter generation, and TTE integration into a single platform — reducing manual process dependency while accelerating administrative services that involve BPKAD, Ditlantas Polda Kalimantan Selatan, and Samsat.

Tech Stack

Laravel, Filament, Livewire, Alpine, MySQL.

Lessons Learned

  • Process before technology: The most valuable work was understanding the actual business process before writing any code. The bottlenecks were process bottlenecks, not technology gaps.
  • Integrate with existing infrastructure: Leveraging Kominfo's TTE service instead of building a proprietary solution reduced development time and ensured legal compliance.
  • Government systems need simplicity: Users across SKPDs have varying technical proficiency. The system had to be simple enough for adoption without extensive training.
  • Single source of truth matters: The moment vehicle data was centralized, the entire organization's relationship with that data changed — from hunting for information to acting on it.

Have a workflow or system to build?

Let's discuss your current operational challenges and how software can help.