POS Capacity Workspace

POS Capacity Management

POS work capacity utilization — multi-POS analysis from Regular & POS support other channel. Upload data, configure parameters, and run target simulations to measure staffing needs and process efficiency.

Input Data

No data yet ▼
Regular · Walk-in POS

Click or drag the Regular file

CSV / XLSX · Columns: POS Name, Month, Walkin, Prospect, Golive, ...
GOTO · 2W

Click or drag the GOTO file

CSV / XLSX · Columns: POS, Month, Appointment, Golive, ...
Regular CSV
Required columns: POS Name · Month · Walkin · Prospect · Golive
GOTO CSV
Required columns: POS · Month · Appointment · Golive
Summary Capacity Category
POS distribution by POS work capacity utilization
Total POS—
Over
—
>85% — high utilization
Medium
—
50–85% — ideal
Low
—
<50% — available
Avg Ideal WI/day
—
at full capacity · all POS avg
Capacity Mix

POS Table

All Over Medium Low
POS ↕ Bln ↕ WI ↕ Pros ↕ GL POS ↕ Sch GOTO ↕ GL GOTO ↕ Used/Cap ↕ Util ↕ Ideal WI Cat ↕
◔

Upload data to start the analysis

Global Configuration

Working Hours & Days

hours
days

PPS fixed activities (min/day)

Time used by PPS for routine non-customer activities each day.
min
min
min
min

Handling Time

Average duration per customer activity.
min
min
min
%
min
times
min
min
Operating hours / day: —
Total PPS fixed activities: —
Available PPS time/day: —
Capacity/month: —

Productivity Simulation · Reverse Capacity

◔

Upload data in the Data tab before running the simulation.

Overview

POS Capacity Management Dashboard

A single-file tool for analyzing and planning POS workload capacity across multiple POS locations. It answers: "Given current or target volumes, is there enough staffing capacity at each POS — and if not, what needs to change?"

Capacity Calculation Framework

Net Working Capacity

Available PPS / day  = Operating hours − Total fixed activities
Capacity / month     = (Available PPS + Available Kapos) × HKE × 60 min
Parameter Default
Operating hours / day8 hours
Effective working days / month22 days
↳ Preparation & briefing1.0 hour
↳ Coordination & communication0.83 hour (50 min)
↳ Reporting & administration1.5 hours (90 min)
↳ Flyering & marketing1.0 hour (60 min)
Total fixed activities4.33 hours (260 min)
Available PPS / day3.67 hours (220 min)
Capacity / month4,840 min

7-Component Time Formula

Every POS row is scored against 7 time components. Utilization = Total Time Used ÷ Capacity per Month.

# Component Formula
1Walk-in screeningWalk-in × 10 min
2Walk-in follow-upWalk-in × 5 min × 3x
3Prospect — input leads & directProspect × 35 min
4Processing GoLive POSGoLive POS × 40 min × 39%
5Schedule follow-upSchedule × 5 min × 3x
6GOTO scheduling (if GOTO active)GOTO Attend × 15 min
7Processing GoLive GOTO (if GOTO active)GOTO GoLive × 55 min

Component 4 uses 39% because only low–medium risk GoLive cases are processed at the POS. GOTO (components 6–7) applies to 2W motorcycle channel only and is not scaled in simulation.

Utilization Tiers
Over
> 85%
Overloaded — risk of service quality drop
Medium
50–85%
Ideal operating range
Low
< 50%
Significant available capacity
Features by Tab

Tab 1 — Data

Upload and view POS performance data. Analyze utilization by month or across all months.

Data Input
Upload FileUpload Regular (walk-in) and GOTO (2W) files. Supports CSV and XLSX/XLS.
Paste CSVPaste raw CSV text directly into the browser.
Load Google SheetAuto-fetch published CSV from Google Sheets. Loads Regular + GOTO simultaneously on page load.
Load SampleLoad built-in demo data (8 POS, January 2026) to explore the tool.
Auto-processData is processed automatically after upload — no button click needed.
Fuzzy POS matchingGOTO file matched to Regular by POS name using Levenshtein distance ≤ 3. Handles minor naming differences.
Required Columns
Regular file
POS Name · Month · Walkin · Prospect · GoLive · Schedule (SVY Start) · NTF
GOTO file
POS · Month · Appointment · GoLive
Table & Views
Month filterFilter chips per month, or "All" for aggregated view.
All months view1 row per unique POS. Utilization shown as average with min–max range (e.g. 72% · 65–80). Click row → trend chart + per-month breakdown.
SortClick any column header to sort ascending/descending.
Search + filterReal-time name search + Over / Medium / Low category chips.
Used/Cap columnTime used and total capacity in one compact column (e.g. 5,970 / 4,840 min) for quick comparison.
Ideal WI columnIdeal walk-in per day at 100% capacity (Regular + GOTO combined), shown inline per POS. Sourced from the Ideal Capacity tab. Updates on any config change.
Export CSVDownload visible rows as CSV.

Tab 2 — Configuration

Adjust all capacity parameters. Changes recalculate the entire data table instantly.

Operating hours / dayNet productive hours per PPS per day (input after personal time). Default: 8.
Effective working daysWorking days excluding public holidays. Default: 22.
PPS fixed activities4 components of non-customer time per day. Total default: 4.33 hours (260 min).
PPTL / Kapos toggleEnable to add Kapos capacity to denominator. 6 fixed activity components for Kapos. Warning shown if total Kapos activities exceed operating hours.
GOTO toggleEnable/disable GOTO components globally across all calculations.
GOTO Capacity CapWhen GOTO is enabled, an optional cap limits how much capacity GOTO consumes per POS. Two modes: % of total capacity — GOTO time budget capped at N% of monthly capacity; Fixed count — GOTO attendances capped at N per month. Affects Ideal Capacity calculation only — historical utilization is unchanged.
Handling time8 parameters covering all 7 formula components: screening, input leads, GoLive processing, GoLive proportion, FU time, FU count, GOTO scheduling, GOTO GoLive.
ApplyRecalculate all data with current config values.
Reset DefaultRestore all fields to framework defaults, then recalculate.

Tab 3 — Simulation

Set a target per POS per month. The dashboard works backwards through the conversion chain to estimate required volume and capacity gap per POS. Two simulation modes are available.

Simulation Modes
Mode Input How it works
Target NTFNTF (Rp) per POS/monthGoLive needed = Target NTF ÷ Ticket Size (per-POS historical). Full reverse chain through CR2 → CR1.
Target GoLiveGoLive contracts/month (same for all POS)Skips ticket size. Same GoLive target applied to all POS. Conversion chain runs from GoLive upward via each POS's own CR2 and CR1.
Reverse Capacity Chain
GoLive needed    = Target NTF ÷ Ticket Size (NTF ÷ GoLive historical)
Prospect needed   = GoLive needed ÷ CR2 (Prospect → GoLive rate)
Walk-in needed    = Prospect needed ÷ CR1 (Walk-in → Prospect rate)
Schedule needed   = Schedule × (Walk-in needed ÷ Walk-in historical)
Time needed       = Recalculate all 7 components
Capacity gap      = Time needed − Capacity per month
Three Recommendation Options
Option Trigger Action
A — Process efficiencyGap can be closed by reducing processing timeShows specific reduction needed (e.g. 40m → 33m/GoLive)
B — Add Kapos supportKapos toggle is ON and there is a gapShows additional Kapos hours/day needed
C — Add PPSGap too large for process efficiency aloneShows number of additional PPS needed
= ceil(Gap ÷ (Available PPS/day × HKE × 60))
Simulation Drawer (per POS)
Volume comparisonHistorical vs projected Walk-in, Prospect, GoLive side-by-side. CR1, CR2, Ticket Size shown.
Time breakdown tableAll 7 components with Historical / Target / Gap columns.
RecommendationsWritten conclusion with Options A, B, C and specific numbers.
Parameter adjustmentOverride handling time, CR1/CR2, GOTO volumes, and Kapos support hours for this POS only. Click Recalculate to update instantly.
Tab 4 — Ideal Capacity

Answers: "How many walk-in customers can each POS handle per month at 100% capacity?" Split into Regular (POS walk-in) and GOTO (2W channel). Based on each POS's historical conversion rates averaged across all loaded months.

Ideal Walk-in Formula
t_goto       = GOTO attend × 15 min + GOTO GoLive × 55 min  (capped if GOTO cap active)
cap_remaining = Capacity/month − t_goto
time_per_wi   = screening + walk-in FU + CR1 × prospect input + CR1 × CR2 × GoLive proc + sched_ratio × FU
ideal_regular = floor(cap_remaining ÷ time_per_wi)
ideal_goto    = historical attend_goto  (or capped count)

CR1, CR2, and sched_ratio (schedule-to-walkin ratio) are derived from each POS's historical averages. When GOTO cap is active in Configuration, GOTO's time budget is reduced, freeing more capacity for Regular walk-in.

Table Columns
Regular/mo · /dayMaximum Regular walk-in per month and per day at full capacity.
GOTO/mo · /dayGOTO attendances per month and per day (historical or capped).
Total/mo · /dayCombined Regular + GOTO capacity. Also shown as "Ideal WI" column in the Data tab table.
Table Features
SortClick any column header to sort ascending/descending. Default: Total/mo descending.
SearchReal-time filter by POS name.
Category filterFilter by current utilization tier (Over / Medium / Low) — useful to focus on overloaded POS.
Export CSVDownloads currently filtered rows only.
Glossary
PPSPoint of Sale Staff — the field agent stationed at the POS
PPTL / KaposTeam leader / area head who can also handle customer capacity when toggled on
Walk-inCustomer who arrives directly at the POS
ProspectWalk-in who progresses to the lead input stage
GoLive POSFinancing contract processed and activated at the POS
GoLive GOTOFinancing contract activated via the GOTO channel (2W motorcycle only)
ScheduleCustomer with an active follow-up appointment in progress
GOTOSeparate inbound channel (agent visits customer) for 2W products only. Not scaled in simulation.
NTFNilai Total Fasilitas — total loan facility value disbursed
Ticket SizeAverage NTF per GoLive unit at a given POS (NTF ÷ GoLive)
CR1Conversion Rate 1 — Walk-in → Prospect (historical average per POS)
CR2Conversion Rate 2 — Prospect → GoLive (historical average per POS)
HKEHari Kerja Efektif — effective working days per month
Capacity GapTime required at target volume minus available capacity. Positive = overloaded.

—

—