Projects

Selected work.

Engagements across ERP, integration, data, and AI — each told with context, approach, and measurable outcomes rather than a list of deliverables.

Project list

  • ERP / Odoo

    ALVA EV — Odoo ERP for Dealer & Distribution

    Delivering Odoo ERP as dealer and distribution system for ALVA EV's electric motorcycle dealer network — system integration and IoT telemetry included. Ongoing engagement as Senior Business Analyst / PM / CoPM for client ALVA EV.

    • Odoo
    • PostgreSQL
    • Python
    • REST APIs
    • IoT (MQTT)
    • n8n
    • Docker

    **Context & Mandate:** ALVA EV — an electric vehicle maker — needed a dealer and distribution system to run its growing dealer network. **Constraints:** Dealer network operations, distribution flows, and telemetry from connected vehicles/devices all needed to work as one system. **Approach:** Odoo ERP delivered as dealer & distribution backbone, with system integration (REST APIs, IoT/MQTT) and automation (n8n) connecting dealer operations to the ERP. **Outcome:** Odoo ERP live as the dealer & distribution system, with IoT telemetry integrated into the platform. **Lessons:** Dealer networks are not warehouses with showrooms — order flows, allocation, and aftersales change everything about an ERP.

    ongoing

  • Automotive / Dealer Systems

    Mitsubishi Dealer Interface

    Implemented dealer-interface system connecting distributor and dealer network — project planning, monitoring, and status reporting across dealer clients. Led development team, delivered per timeline.

    • .NET Framework
    • C#
    • MS SQL Server
    • Web Services

    **Context & Mandate:** The dealer network needed a dealer-interface system connecting distributor and dealer operations. **Constraints:** Multiple dealer clients with different operating rhythms; delivery had to stay on schedule. **Approach:** Created and executed project plan and procedures, ran progress meetings with distributor and dealer clients, monitored and reported project status. Led the development team throughout. **Outcome:** Dealer-interface system implemented across the network, delivered per timeline with management reporting in place. **Lessons:** Dealer clients need a single mouthpiece — one PM owning the plan, the meetings, and the status keeps a network project honest.

    completed

  • Utilities / Enterprise Systems

    Customer Information & Management Systems — PLN

    Designed & developed customer information and management systems for PLN electricity distribution — new connection, meter reading, billing, payment, and credit control features across distribution units.

    • .NET / C#
    • Oracle
    • SQL Server
    • Web Services

    **Context & Mandate:** General electricity utilities needed customer information systems (CIS) to manage customers end-to-end. **Constraints:** Multiple distribution units (East Java, Jakarta), each with its own operational flows; a mix of legacy systems to customize and new modules to build. **Approach:** Designed and developed NetCIS (Customer Information System) on .NET + Oracle; developed CMS for PLN Distribusi Jawa Timur; customized and implemented CISRISI (new connection, meter reading, billing, payment, credit control) with end-user training. **Outcome:** Customer information & management features delivered across PLN distribution units. **Lessons:** Utility billing logic is deceptively complex — meter reading, billing, payment, and credit control must be modeled as one process, not four features.

    completed

Case study approach

Every case study follows the same discipline — the same questions, answered in the same order.

  • Context & Mandate — the business problem, and why this project, why then.
  • Constraints — budget, timeline, legacy systems, organizational dynamics.
  • Approach — architecture decisions, methodology, team composition, risk mitigation.
  • Outcome — measurable results: performance, cost, adoption, revenue, risk reduction.
  • Lessons — what worked, what didn't, and what I'd do differently.