All projects

Lensa Inventory

PT. Telkom Akses · Internal enterprise system · Jan 2021 – Present

Nationwide warehouse management system that controls material usage and prevents fraud across 451 warehouses.

  • Laravel 12
  • Microservices
  • API Gateway
  • SAP
  • Redis
  • Kibana
SAP ERPLENSA MOBILETACTICAL PROAPIGATEWAYLENSA INVENTORYLaravel 12REDISKIBANA451 warehouses · 32 areas

Architecture overview — internal system, diagram shown in place of screenshots.

01Problem Solved

Material used by field technicians across hundreds of warehouses nationwide was hard to track and control. Without one reliable record of who took which material, from where, and for which job, usage was inefficient and open to fraud.

02Solution

A centralized warehouse management system that records every material reservation and usage per technician and per warehouse. It connects to SAP (ERP) for stock and material data, to the Lensa Mobile app used by technicians in the field, and to Tactical Pro for technician and area management — all through an API Gateway.

03Key Features

  • Material reservation and usage tracking per technician, job, and warehouse
  • Stock management across 32 service areas and 451 warehouses
  • Integration with SAP (ERP) for material and stock data
  • API integration with the Lensa Mobile technician app and Tactical Pro (area mapping, field coordinators, heads)
  • Monitoring and reporting for usage control and fraud prevention
  • Centralized logging and monitoring with Kibana

04Technologies Used

  • Laravel 12
  • PHP
  • MySQL
  • Microservices
  • API Gateway
  • Redis
  • Queue
  • Scheduler
  • SAP integration
  • Kibana

05Challenges & Solutions

Challenge

Daily nationwide load

~4,000 technicians active every day.

Solution

Used Redis caching for frequently read data and queues for high-volume processing so the app stays fast and stable.

Challenge

Integrating with SAP and external apps

Several systems owned by different teams.

Solution

Standardized communication through an API Gateway with clear API contracts, and traced issues with centralized logs in Kibana.

Challenge

Rolling out to 451 warehouses

A failed launch would disrupt field operations.

Solution

Ran UAT and piloting with selected areas before go-live, with an operations team handling post-production support.

Challenge

Recurring background work

Sync jobs and recaps.

Solution

Moved it to scheduled jobs instead of manual processes.

06My Role

Back-end Developer & Project Lead

  • Designed the system architecture and database structure (ERD).
  • Built back-end services and APIs in Laravel 12 with a microservices approach.
  • Since Jul 2025, led a cross-functional team of 10 (5 developers, 1 QA, 1 infra, 3 operations) through requirements, UAT, piloting, and go-live.
  • Coordinated with the Lensa Mobile, Tactical Pro, and SAP teams.

07Business Impact

  • Used by 19,000+ field technicians nationwide, with ~4,000 active per day.
  • One system covering 32 service areas and 451 warehouses.
  • Gives management traceable material usage per technician, which supports fraud prevention and efficient material control.

Want to hear more about how this was built?

Let's Talk