{ "schema_version": "1.1.0", "document": { "id": "aizen-business-glossary", "title": "AIZEN Business Glossary", "language": "en", "status": "reference", "last_updated": "2026-11-02", "live_data": false, "reference_scope": "Essential business definitions, recorded statuses, and source-specific reporting rules. Conflicts are qualified; source code, PRD intent, and glossary conventions are not interchangeable." }, "interpretation": { "current": "An existing label or attribute; its business meaning may still need confirmation.", "reference": "A working business definition, not a claim of formal approval.", "needs_decision": "True flags an unresolved threshold, source conflict, policy, or entity mapping. Inclusion preserves a useful term without adopting an unverified rule; false does not establish approval.", "numeric_policy": "Thresholds and formulas are definitions or working policies, not observed warehouse KPI results.", "extraction_path": "$.groups[*].terms[*]", "aliases": "Equivalent names or existing UI labels. search_keywords are related lookup terms, not synonyms or policy mappings.", "entity": "The entity or domain described by a term; counting units, cohorts, and denominators still follow its definition.", "reporting_conventions": "Fleet and DPD conventions are source-specific. The dashboard uses snapshot DEFAULT buckets and an ACTIVE, trailing-seven-day, non-DEFAULT earning numerator. Calendar-day DPD and report-date-only earning are separate conventions; do not silently substitute them.", "counting_units": "Fleet counts use unique vehicle IDs. Person, account, application, contract, vehicle, and event counts are distinct. Repeat applications count as separate applications, not automatically separate people or handovers.", "reconciliation": "With complete coverage at one cutoff: Eligible Fleet = Earning Eligible Vehicles + Previously-Handed-Over Idle; Total Idle = Never-Handed-Over Idle + Previously-Handed-Over Idle. Groups are mutually exclusive within their population; breakdowns equal totals.", "source_status": "Source observations are pinned code or query definitions, not production verification. PRD status Done is document metadata, not proof of deployment or policy approval." }, "groups": [ { "id": "business", "title": "Business & ownership", "description": "Who we serve, who owns the asset, and who funds it.", "terms": [ { "name": "B2B", "definition": "Electric vehicles supplied at scale to business clients through rental or RTO arrangements.", "note": "Monthly invoicing is a repayment process. Program and commercial arrangement, including a genuine sale-and-leaseback, remain separate classifications.", "aliases": [ "Business-to-Business" ], "formula": "", "technical": "The recorded VehicleType enum includes MOTORCYCLE, CAR, and TRUCK. State the actual vehicle-type coverage of each report; enum support alone does not establish a deployed fleet.", "origin": "reference", "section": "Business relationship", "id": "business-b2b", "related": [], "type": "definition", "needs_decision": false, "entity": "commercial_structure", "search_keywords": [ "business to business", "corporate" ], "pending_decision_ids": [] }, { "name": "B2C", "definition": "Rent-to-Own or Rent Only provided directly to individual customers.", "note": "B2C vehicles remain registered under AIZEN during the contract. Any ownership transfer is handled separately after the contractual requirements are fulfilled.", "aliases": [ "Business-to-Consumer" ], "formula": "", "technical": "", "origin": "reference", "section": "Business relationship", "id": "business-b2c", "related": [], "type": "definition", "needs_decision": false, "entity": "commercial_structure", "search_keywords": [ "business to consumer", "retail" ], "pending_decision_ids": [] }, { "name": "B2B2C", "definition": "An intermediary-based commercial relationship connecting business partners with individual customers.", "note": "RF remains a B2B2C program in the business taxonomy. Some reports place RF under a B2C reporting segment; do not add both classifications together.", "aliases": [], "formula": "", "technical": "Dashboard segment_of maps RF-prefixed program names to B2C RF. This reporting label does not change the business-model decision.", "origin": "reference", "section": "Business relationship", "id": "business-b2b2c", "related": [], "type": "definition", "needs_decision": false, "entity": "commercial_structure", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Sale-and-Leaseback", "definition": "AIZEN purchases assets from a seller and leases those assets back to that same seller.", "note": "The seller becomes the lessee. Ordinary purchases from an OEM followed by B2B rental or B2C RTO are not S&L.", "aliases": [ "SLB", "S&L", "Sale and Leaseback" ], "formula": "", "technical": "", "origin": "reference", "section": "Commercial arrangement", "id": "business-sale-and-leaseback", "related": [], "type": "definition", "needs_decision": false, "entity": "commercial_structure", "search_keywords": [ "SLB", "S&L", "sale and leaseback" ], "pending_decision_ids": [] } ] }, { "id": "programs", "title": "Program types", "description": "The product terms, independent of the customer segment.", "terms": [ { "name": "Rent Only (Rental)", "definition": "Use of a vehicle for rental payments, with return of the vehicle at program completion rather than an ownership-transfer entitlement.", "note": "The SOP calls this Rent Only. It describes a manual Finance billing/payment process for Rent Only; do not assume the RTO automatic daily-billing process applies unchanged.", "aliases": [ "Rent", "Rental", "Rent Only" ], "formula": "", "technical": "", "origin": "reference", "section": "Product definitions", "id": "programs-rental", "related": [], "type": "definition", "needs_decision": false, "entity": "product", "search_keywords": [ "Rent" ], "pending_decision_ids": [] }, { "name": "RTO", "definition": "Rent-to-Own: a program allowing a customer or client to obtain ownership after fulfilling the agreed contractual requirements.", "note": "For B2C, the SOP separates final repayment, document title transfer, document handover, deposit return, and account closure. B2B RTO follows its own agreement; payment completion alone does not prove legal transfer.", "aliases": [ "Rent-to-Own" ], "formula": "", "technical": "", "origin": "reference", "section": "Product definitions", "id": "programs-rto", "related": [], "type": "definition", "needs_decision": false, "entity": "product", "search_keywords": [ "rent to own" ], "pending_decision_ids": [] }, { "name": "RF (Retail Financing)", "definition": "Retail Financing: a B2B2C program in which AIZEN acts as an intermediary and a financing institution (Multi Finance) assesses credit and approves financing.", "note": "Affiliate Partners may provide leads, wallet deductions, and repayment reports under their agreement. Wallet deduction, remittance to AIZEN, and repayment to Multi Finance are separate events; legal ownership is recorded separately.", "aliases": [ "RF", "Retail Financing" ], "formula": "", "technical": "Dashboard reporting groups this program as B2C RF. Reconcile program and business-model populations before comparing B2C and B2B2C totals.", "origin": "reference", "section": "Product definitions", "id": "programs-rf", "related": [], "type": "definition", "needs_decision": false, "entity": "product", "search_keywords": [ "Bukopin" ], "pending_decision_ids": [] } ] }, { "id": "vehicle", "title": "Vehicles", "description": "Separate operational status, recovery progress, and remote lock.", "terms": [ { "name": "Vehicle ACTIVE", "definition": "An existing vehicle status indicating active use under source-system rules.", "note": "Does not independently prove earning, payment quality, or physical possession.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-vehicle-active", "related": [], "type": "status", "needs_decision": false, "entity": "vehicle", "search_keywords": [], "pending_decision_ids": [] }, { "name": "READY_TO_HANDOVER", "definition": "A vehicle available for the handover workflow after the required operational checks.", "note": "Credit Connect uses this status for handover creation and after eligible QC or repair completion. It does not by itself confirm a reservation or a universal “Ready to Rent” classification.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-ready-to-handover", "related": [ "vehicle-in-qc", "application-handover-pending" ], "type": "status", "needs_decision": true, "entity": "vehicle", "search_keywords": [ "ready to handover", "ready to rent" ], "pending_decision_ids": [] }, { "name": "IN_REPAIR", "definition": "An existing status for vehicles undergoing repair or maintenance.", "note": "In Credit Connect, service completion returns the vehicle to ACTIVE or READY_TO_HANDOVER based on its history before QC.", "aliases": [ "Under Repair" ], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-in-repair", "related": [ "vehicle-in-qc", "vehicle-ready-to-handover" ], "type": "status", "needs_decision": false, "entity": "vehicle", "search_keywords": [ "under repair", "maintenance" ], "pending_decision_ids": [] }, { "name": "IN_QC", "definition": "A vehicle undergoing quality inspection before return to use or preparation for handover.", "note": "In Credit Connect, QC can lead to repair, ACTIVE, or READY_TO_HANDOVER depending on inspection and prior history. Reporting it as repair or idle still needs an agreed mapping.", "aliases": [ "Quality Control", "QC" ], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-in-qc", "related": [ "vehicle-in-repair", "vehicle-ready-to-handover" ], "type": "status", "needs_decision": true, "entity": "vehicle", "search_keywords": [ "quality control", "QC" ], "pending_decision_ids": [] }, { "name": "INACTIVE vehicle", "definition": "An existing vehicle status requiring a more specific reason.", "note": "Does not by itself establish availability, retirement, loss, or customer possession.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-inactive-vehicle", "related": [], "type": "status", "needs_decision": true, "entity": "vehicle", "search_keywords": [], "pending_decision_ids": [] }, { "name": "PENDING vehicle", "definition": "An existing vehicle status whose operational meaning needs confirmation.", "note": "Separate from PENDING_COLLECTION, which explicitly means a collection request. PENDING alone does not justify excluding a vehicle from owned stock.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-pending-vehicle", "related": [ "vehicle-pending-collection" ], "type": "status", "needs_decision": true, "entity": "vehicle", "search_keywords": [], "pending_decision_ids": [] }, { "id": "vehicle-pending-collection", "name": "PENDING_COLLECTION", "definition": "A vehicle flagged for collection, before collection work starts.", "note": "In Credit Connect, Request Collection sets this status; Start Collection moves it to IN_COLLECTION. Neither confirms that the vehicle has been recovered.", "aliases": [ "Pending Collection" ], "search_keywords": [ "collection request", "permintaan penarikan" ], "formula": "", "technical": "", "origin": "current", "needs_decision": false, "section": "Current statuses", "entity": "vehicle", "type": "status", "related": [ "vehicle-in-collection", "handover-physical-vehicle-recovery" ], "pending_decision_ids": [] }, { "name": "IN_COLLECTION", "definition": "Vehicle collection or recovery work is in progress.", "note": "Credit Connect can mark the linked contract CHURNED when collection starts. This status alone does not confirm physical recovery; receipt evidence is still needed.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-in-collection", "related": [ "vehicle-pending-collection", "handover-physical-vehicle-recovery", "contract-churned" ], "type": "status", "needs_decision": true, "entity": "vehicle", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Vehicle PAID_OFF", "definition": "A vehicle carrying the source system’s paid-off financial label.", "note": "Verify settlement against the contract. This label alone does not establish legal ownership transfer.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "vehicle-vehicle-paid-off", "related": [ "contract-completed", "contract-b2c-rto-program-completion" ], "type": "status", "needs_decision": false, "entity": "vehicle", "search_keywords": [], "pending_decision_ids": [] }, { "id": "vehicle-remote-unit-lock", "name": "Remote Unit Lock", "definition": "An instruction to lock a vehicle remotely through its IoT provider.", "note": "Operational vehicle status, reported lock state, and command progress are separate. Sending a command does not confirm the vehicle is locked.", "aliases": [ "Remote Lock" ], "search_keywords": [ "LOCKED", "UNLOCKED", "IoT", "kunci jarak jauh" ], "formula": "", "technical": "VehicleRemoteLockCommandStatus: PENDING, IN_PROGRESS, SUCCEEDED, FAILED, TIMED_OUT. These values describe command execution; VehicleLockStatusEnum separately records LOCKED/UNLOCKED. Preserve provider/state evidence before asserting a physical lock.", "origin": "reference", "needs_decision": false, "section": "Vehicle controls", "entity": "vehicle_control", "type": "definition", "related": [ "vehicle-locked", "vehicle-in-collection", "handover-physical-vehicle-recovery" ], "pending_decision_ids": [] }, { "id": "vehicle-locked", "name": "Vehicle LOCKED", "definition": "The LOCKED operational label on a vehicle record.", "note": "It is separate from the reported LOCKED/UNLOCKED lock state and from the progress of a remote command.", "technical": "VehicleStatusEnum retains LOCKED; VehicleLockStatusEnum and VehicleRemoteLockCommandStatus are separate fields and records.", "formula": "", "aliases": [], "search_keywords": [], "entity": "vehicle", "section": "Current statuses", "origin": "current", "needs_decision": false, "type": "status", "related": [ "vehicle-remote-unit-lock" ], "pending_decision_ids": [] } ] }, { "id": "contract", "title": "Contracts", "description": "Keep lifecycle separate from payment risk and exit reasons.", "terms": [ { "name": "COMPLETED", "definition": "A contract that has fulfilled its contractual completion requirements.", "note": "In Credit Connect, completion requires no remaining installments and no unpaid, processing, or partly paid bills. Legal ownership transfer is verified separately.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Lifecycle", "id": "contract-completed", "related": [ "contract-b2c-rto-program-completion", "contract-rf-program-completion" ], "type": "status", "needs_decision": false, "entity": "contract", "search_keywords": [], "pending_decision_ids": [] }, { "id": "contract-churned", "name": "Contract CHURNED", "definition": "A contract ended through the churn workflow rather than normal contractual completion.", "note": "In Credit Connect, an ACTIVE or DEFAULT contract can move to CHURNED. This does not by itself confirm customer blacklisting, debt settlement, or physical vehicle recovery.", "aliases": [ "CHURNED" ], "search_keywords": [ "contract exit", "churn", "kontrak berakhir" ], "formula": "", "technical": "Pinned code moves ACTIVE or DEFAULT contracts to CHURNED. PRD 742883329 uses customer-level Churned/Blacklisted outcomes, while the recorded CustomerStatus enum has ACTIVE/INACTIVE. Keep entity mapping unresolved instead of copying this status to customer records.", "origin": "current", "needs_decision": true, "section": "Lifecycle", "entity": "contract", "type": "status", "related": [ "contract-completed", "customer-customer-blacklisted", "handover-physical-vehicle-recovery" ], "pending_decision_ids": [] }, { "name": "Recorded DEFAULT", "definition": "A contract carrying the DEFAULT status in the source system.", "note": "Recorded DEFAULT and reporting DEFAULT are separate fields. Thresholds differ across PRDs and reports; neither implies the vehicle is idle or billing has stopped.", "aliases": [ "Contract DEFAULT" ], "formula": "", "technical": "Pinned Credit Connect derives DEFAULT from at least four late bills. PRD 385744907 says DPD >2; PRD 19431425 describes 120 hours. These are documented differences, not verified equivalent production rules.", "origin": "current", "section": "Existing values to clarify", "id": "contract-recorded-default", "related": [ "payment-default", "payment-dpd", "payment-late-bill-count" ], "type": "status", "needs_decision": true, "entity": "contract", "search_keywords": [ "contract default", "recorded default" ], "pending_decision_ids": [] }, { "id": "contract-b2c-rto-program-completion", "name": "B2C RTO Program Completion", "definition": "The completion workflow covering document title transfer, document collection, deposit return, and borrower-account closure after the final repayment milestone.", "note": "Keep settlement, legal transfer, document handover, and account closure as distinct events; do not assume they share one timestamp.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "Program completion", "entity": "contract_event", "type": "definition", "related": [], "pending_decision_ids": [] }, { "id": "contract-rf-program-completion", "name": "RF Program Completion", "definition": "The RF completion process in which final installment repayment is followed by financial-institution notification and BPKB handover.", "note": "The SOP assigns BPKB handover to the financial institution; do not substitute the B2C RTO completion workflow.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "Program completion", "entity": "contract_event", "type": "definition", "related": [], "pending_decision_ids": [] }, { "name": "Contract ACTIVE", "definition": "A contract currently in force.", "note": "Payment health is tracked separately: an ACTIVE contract can have overdue bills. Credit Connect records DEFAULT as a separate contract status.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "contract-contract-active", "related": [ "contract-recorded-default", "payment-late-bill-count" ], "type": "status", "needs_decision": false, "entity": "contract", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Contract BLACKLISTED", "definition": "An existing contract status requiring confirmation of its exit and restriction semantics.", "note": "Preserve contract history. Do not automatically infer a customer blacklist flag.", "aliases": [], "formula": "", "technical": "PRD 742883329 describes Blacklisted as final; Draft Layer Approval 759300097 allows exceptions. Pinned application approval code can reopen a customer restriction while leaving the historical application BLACKLISTED. Do not infer permanence or propagate flags across entities.", "origin": "current", "section": "Current statuses", "id": "contract-contract-blacklisted", "related": [ "customer-customer-blacklisted" ], "type": "status", "needs_decision": true, "entity": "contract", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Contract DRAFT", "definition": "A pre-activation contract record.", "note": "Credit Connect retains legacy contract-onboarding states. A DRAFT contract record is separate from an application draft or a legal document awaiting signature.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "contract-contract-draft", "related": [], "type": "status", "needs_decision": true, "entity": "contract", "search_keywords": [], "pending_decision_ids": [] }, { "id": "contract-legacy-statuses", "name": "Legacy Contract Statuses", "definition": "Contract-level onboarding and older status labels retained alongside the application-led flow.", "note": "Always state the entity and source version. Matching names across application and contract records do not prove the same event.", "technical": "CustomerContractStatus retains INITIATED, IN_REVIEW, SCHEDULING, HANDOVER_PENDING, HANDOVER_PROCESS, REJECTED and SOFT_REJECTED. INACTIVE, PENDING_VERIFICATION, NEED_REVIEW, WAITING_FOR_HANDOVER are deprecated. These enum values are not a universal migration or transition order.", "formula": "", "aliases": [], "search_keywords": [], "entity": "contract", "section": "Current statuses", "origin": "current", "needs_decision": true, "type": "status", "related": [], "pending_decision_ids": [] } ] }, { "id": "customer", "title": "Customer statuses", "description": "Customer record status and restrictions, separate from contract and application progress.", "terms": [ { "name": "Customer ACTIVE", "definition": "A customer record marked ACTIVE in EMMS.", "note": "Credit Connect sets this status during handover activation. Contract status, payment health, and login permissions are separate.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "customer-customer-active", "related": [ "contract-contract-active", "customer-customer-inactive" ], "type": "status", "needs_decision": true, "entity": "customer", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Customer INACTIVE", "definition": "A customer record marked INACTIVE in EMMS.", "note": "An INACTIVE customer can still have a lead or blacklist flag. This status alone does not establish contract history or login permissions.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Current statuses", "id": "customer-customer-inactive", "related": [ "customer-customer-active", "customer-customer-blacklisted" ], "type": "status", "needs_decision": true, "entity": "customer", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Customer Blacklisted", "definition": "A customer restriction flag with a reason, effective date, and review or removal policy.", "note": "Not a lifecycle state; do not automatically derive it from contract or application labels.", "aliases": [ "is_blacklisted" ], "formula": "", "technical": "PRD 742883329 describes Blacklisted as final; Draft Layer Approval 759300097 allows exceptions. Pinned application approval code can reopen a customer restriction while leaving the historical application BLACKLISTED. Do not infer permanence or propagate flags across entities.", "origin": "current", "section": "Current statuses", "id": "customer-customer-blacklisted", "related": [], "type": "status", "needs_decision": true, "entity": "customer", "search_keywords": [ "is_blacklisted", "blacklist" ], "pending_decision_ids": [] } ] }, { "id": "application", "title": "Application & acquisition", "description": "Distinguish people, applications, workflow stages, and cohorts.", "terms": [ { "name": "IN_REVIEW", "definition": "An application in verification and video review after credit approval in the application-led flow.", "note": "SCHEDULING follows approval of submitted video or a NOT_REQUIRED video path; credit approval alone does not confirm handover readiness.", "aliases": [], "formula": "", "technical": "Video state is separate from ApplicationStatus: NOT_STARTED, NOT_REQUIRED, WAITING_VIDEO, SUBMITTED, RETAKE_REQUIRED. A retake can leave the application IN_REVIEW.", "origin": "current", "section": "Application workflow", "id": "application-in-review", "related": [], "type": "status", "needs_decision": false, "entity": "application", "search_keywords": [ "application workflow" ], "pending_decision_ids": [] }, { "name": "SCHEDULING", "definition": "An application eligible for handover scheduling.", "note": "A reserved slot does not itself confirm commitment-fee payment or physical delivery.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Application workflow", "id": "application-scheduling", "related": [], "type": "status", "needs_decision": false, "entity": "application", "search_keywords": [ "application workflow" ], "pending_decision_ids": [] }, { "name": "HANDOVER_PENDING", "definition": "In Credit Connect’s application-led flow, an application awaiting handover after commitment-fee settlement and schedule reservation.", "note": "A pending handover is not a completed delivery.", "aliases": [], "formula": "", "technical": "Pinned application code settles the booking fee with a reserved schedule before HANDOVER_PENDING. PRDs differ on whether deposit falls due in HANDOVER_PENDING or HANDOVER_PROCESS; the mobile application flow exposes its deposit card in HANDOVER_PROCESS.", "origin": "current", "section": "Application workflow", "id": "application-handover-pending", "related": [], "type": "status", "needs_decision": true, "entity": "application", "search_keywords": [ "application workflow" ], "pending_decision_ids": [] }, { "name": "HANDOVER_PROCESS", "definition": "An application undergoing handover processing.", "note": "Not a completed physical handover.", "aliases": [], "formula": "", "technical": "Pinned application code confirms the deposit in HANDOVER_PROCESS after commitment-fee settlement. PRDs place the deposit gate at different stages; do not infer one universal due date from the status.", "origin": "current", "section": "Application workflow", "id": "application-handover-process", "related": [], "type": "status", "needs_decision": true, "entity": "application", "search_keywords": [ "application workflow" ], "pending_decision_ids": [] }, { "name": "CONTRACT_GENERATED", "definition": "An application that has been linked to its newly created customer contract.", "note": "Keep the application’s history separate from contract servicing and physical-delivery evidence.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Application workflow", "id": "application-contract-generated", "related": [], "type": "status", "needs_decision": false, "entity": "application", "search_keywords": [ "application workflow" ], "pending_decision_ids": [] }, { "name": "REJECTED", "definition": "An application declined following assessment.", "note": "Keep customer restrictions separate.", "aliases": [], "formula": "", "technical": "", "origin": "current", "section": "Assessment outcome", "id": "application-rejected", "related": [], "type": "status", "needs_decision": false, "entity": "application", "search_keywords": [ "application workflow" ], "pending_decision_ids": [] }, { "id": "application-draft-application", "name": "DRAFT application", "definition": "An application saved before submission.", "note": "This is an application record, not a signed contract or a count of unique people.", "technical": "Submission moves DRAFT to INITIATED. Customer ID, Application ID, and Contract ID identify different records; one customer can have repeat applications.", "formula": "", "aliases": [], "search_keywords": [], "entity": "application", "section": "Current statuses", "origin": "current", "needs_decision": false, "type": "status", "related": [], "pending_decision_ids": [] }, { "id": "application-initiated", "name": "INITIATED", "definition": "A submitted application awaiting credit assessment.", "note": "It is not an active contract. Approval in the application-led flow moves it to IN_REVIEW.", "technical": "", "formula": "", "aliases": [], "search_keywords": [], "entity": "application", "section": "Current statuses", "origin": "current", "needs_decision": false, "type": "status", "related": [ "application-draft-application", "application-in-review" ], "pending_decision_ids": [] }, { "id": "application-soft-rejected", "name": "SOFT_REJECTED", "definition": "A rejection-related application value retained in the source system.", "note": "The schema marks it deprecated for new data, but recorded code paths and web filters still use it. Do not infer reapplication eligibility.", "technical": "Pinned application.entity.ts still assigns this value in rejection paths. Runtime use depends on the route; schema deprecation alone does not establish that writes have stopped.", "formula": "", "aliases": [], "search_keywords": [], "entity": "application", "section": "Current statuses", "origin": "current", "needs_decision": true, "type": "status", "related": [], "pending_decision_ids": [] }, { "id": "application-application-blacklisted", "name": "Application BLACKLISTED", "definition": "An application recorded as blacklisted or restricted.", "note": "This historical application status is separate from the customer’s current restriction flag.", "technical": "OPEN_BLACKLIST can reopen the customer as a lead while the old application remains BLACKLISTED. PRD finality and exception rules differ.", "formula": "", "aliases": [], "search_keywords": [], "entity": "application", "section": "Current statuses", "origin": "current", "needs_decision": true, "type": "status", "related": [ "customer-customer-blacklisted", "contract-contract-blacklisted" ], "pending_decision_ids": [] } ] }, { "id": "handover", "title": "Handover & recovery", "description": "Separate physical events, documents, and ledger entries.", "terms": [ { "name": "BAST", "definition": "A document acknowledging a specified handover or receipt between named parties.", "note": "The SOP uses BAST for OEM-to-AIZEN receipt, customer/client vehicle handover, collected-unit warehouse receipt, and BPKB handover. A BAST record is not automatically a new customer deployment.", "aliases": [ "Berita Acara Serah Terima" ], "technical": "", "formula": "", "origin": "reference", "section": "Delivery & documentation", "id": "handover-bast", "related": [ "handover-b2c-billing-start", "handover-physical-vehicle-recovery" ], "type": "definition", "needs_decision": false, "entity": "handover_document", "search_keywords": [ "serah terima", "handover document" ], "pending_decision_ids": [] }, { "name": "Physical Vehicle Recovery", "definition": "Confirmed physical retrieval of a vehicle, with a recovery date and receipt evidence.", "note": "Record the recovery date and receiving custodian. In RF, recovery can precede a later handover to AIZEN; a contract exit, remote lock, or collection initiation does not confirm physical recovery.", "aliases": [], "formula": "", "technical": "", "origin": "reference", "section": "Recovery & re-rental", "id": "handover-physical-vehicle-recovery", "related": [ "vehicle-in-collection", "vehicle-remote-unit-lock", "handover-bast" ], "type": "definition", "needs_decision": false, "entity": "vehicle_event", "search_keywords": [], "pending_decision_ids": [] }, { "id": "handover-b2c-billing-start", "name": "B2C Billing Start", "definition": "The effective start date of a B2C contract’s billing schedule.", "note": "Use the contract’s billing start date. Physical handover, the first chargeable installment, and cash receipt can fall on different dates.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "Delivery & documentation", "entity": "contract_event", "type": "definition", "related": [ "handover-bast", "payment-initial-paid-billing", "payment-cash-received" ], "pending_decision_ids": [] }, { "id": "handover-multi-finance-disbursement", "name": "Multi Finance Disbursement", "definition": "Release or activation of financing by Multi Finance under the relevant facility.", "note": "The SOP places B2C unit disbursement on handover day and B2B financing activation one day after client delivery. Do not use one universal disbursement-to-handover date rule.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "Financing & delivery", "entity": "financing_event", "type": "definition", "related": [], "pending_decision_ids": [] }, { "id": "handover-physical-handover", "name": "Physical Handover", "definition": "Confirmed physical delivery of a vehicle to an individual customer or corporate client.", "note": "First handover is the vehicle’s first customer delivery; repeat handover is a later customer delivery. Warehouse or city transfers are separate events. Use the actual event date and location; later moves do not rewrite history.", "formula": "", "technical": "Record the event type and unique vehicle ID. Repeat applications or contracts do not themselves prove another physical handover.", "aliases": [ "Customer Handover" ], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Handover events", "entity": "vehicle_event", "type": "definition", "related": [ "handover-bast", "fleet-eligible-fleet" ], "pending_decision_ids": [] }, { "id": "handover-voluntary-return", "name": "Voluntary Return", "definition": "A customer voluntarily hands the vehicle back to AIZEN or its designated custodian.", "note": "Record physical receipt separately from the reason for return. This is distinct from repossession and does not itself settle debt or close the contract.", "formula": "", "technical": "", "aliases": [], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Return & recovery", "entity": "vehicle_event", "type": "definition", "related": [ "handover-physical-vehicle-recovery", "contract-churned" ], "pending_decision_ids": [] }, { "id": "handover-takeover", "name": "Takeover (RTO Unit)", "definition": "Reuse of a previously handed-over vehicle under a subsequent customer agreement.", "note": "A reuse proxy is not proof of a new physical handover or a universally agreed RTO billing rule.", "technical": "Dashboard V04 requires handover rank ≥2 plus handover within 45 days of the selected contract entry date. PRDs 571637763/374669313 use different <30/>30-day billing rules and leave exactly 30 days undefined. Legacy dbt reuse cohorts also differ; do not merge these definitions.", "formula": "", "aliases": [ "Take over" ], "search_keywords": [], "entity": "vehicle_event", "section": "Handover events", "origin": "reference", "needs_decision": true, "type": "definition", "related": [ "handover-physical-handover" ], "pending_decision_ids": [] } ] }, { "id": "payment", "title": "Payment & delinquency", "description": "Separate bills, cash, balances, and payment-risk events.", "terms": [ { "name": "Chargeable Billing", "definition": "Bills or bill components that create a customer payment obligation under the applicable program rules.", "note": "Use actual payable components: free billing can leave fees due. Chargeable billing is a payment obligation, not cash received or accounting revenue.", "aliases": [], "formula": "", "technical": "", "origin": "reference", "section": "Billing, cash & balances", "id": "payment-chargeable-billing", "related": [ "payment-billing", "payment-cash-received", "payment-free-billing", "payment-hold-billing" ], "type": "definition", "needs_decision": false, "entity": "contract_payment", "search_keywords": [], "pending_decision_ids": [] }, { "id": "payment-cash-received", "name": "Cash Received", "definition": "Actual cash receipts during the reporting period, measured by receipt date.", "note": "Separate installments, deposits, fees, and refunds. In RF, a driver-wallet deduction is distinct from the AP remittance received by AIZEN.", "aliases": [ "Cash Collected", "Cash Receipts" ], "search_keywords": [ "penerimaan kas" ], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "Billing, cash & balances", "entity": "payment", "type": "definition", "related": [ "payment-chargeable-billing", "payment-settled-billing" ], "pending_decision_ids": [] }, { "name": "Settled Billing", "definition": "Bills fully resolved through payments or valid adjustments.", "note": "Not equivalent to cash received: receipt and bill dates differ, and adjustments may be noncash.", "aliases": [ "Settled Bills" ], "formula": "", "technical": "", "origin": "reference", "section": "Billing, cash & balances", "id": "payment-settled-billing", "related": [ "payment-cash-received", "payment-outstanding-balance" ], "type": "definition", "needs_decision": false, "entity": "contract_payment", "search_keywords": [ "paid bills", "settled bills" ], "pending_decision_ids": [] }, { "name": "Outstanding Balance", "definition": "Remaining obligations after allocated payments and valid adjustments.", "note": "Includes both overdue and not-yet-due amounts.", "aliases": [], "formula": "", "technical": "", "origin": "reference", "section": "Billing, cash & balances", "id": "payment-outstanding-balance", "related": [ "payment-arrears", "payment-settled-billing" ], "type": "definition", "needs_decision": false, "entity": "contract_payment", "search_keywords": [], "pending_decision_ids": [] }, { "name": "Arrears", "definition": "The overdue portion of outstanding balance after allocated payments and valid adjustments.", "note": "Do not assume the full original bill remains due when partial allocations exist.", "aliases": [], "formula": "", "technical": "", "origin": "reference", "section": "Billing, cash & balances", "id": "payment-arrears", "related": [ "payment-outstanding-balance", "payment-dpd" ], "type": "definition", "needs_decision": false, "entity": "contract_payment", "search_keywords": [], "pending_decision_ids": [] }, { "id": "payment-daily-deduction-engine", "name": "Daily Deduction Engine (RF)", "definition": "The RF process in which the Affiliate Partner arranges driver-wallet deductions and reports repayment activity to AIZEN.", "note": "Credit Connect also uses DDE for GoPay autocharge. That flow, RF partner-wallet deductions, and AP remittances are separate.", "aliases": [ "DDE" ], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "RF repayment flows", "entity": "payment_process", "type": "definition", "related": [ "payment-ap-remittance-to-aizen", "payment-aizen-repayment-to-multi-finance" ], "pending_decision_ids": [] }, { "id": "payment-ap-remittance-to-aizen", "name": "AP Remittance to AIZEN", "definition": "Payment from the Affiliate Partner to AIZEN for RF customers under the monthly remittance process.", "note": "This is separate from the daily customer-wallet deductions and from onward payment to Multi Finance.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "RF repayment flows", "entity": "payment", "type": "definition", "related": [], "pending_decision_ids": [] }, { "id": "payment-aizen-repayment-to-multi-finance", "name": "AIZEN Repayment to Multi Finance", "definition": "AIZEN payment to the financing institution under the financing schedule.", "note": "This is AIZEN’s financing outflow, not customer installment cash received.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "RF repayment flows", "entity": "payment", "type": "definition", "related": [], "pending_decision_ids": [] }, { "id": "payment-backcharge", "name": "Backcharge", "definition": "An adjustment that reduces the amount to be charged on the B2B client invoice under the SOP.", "note": "Record its reason and supporting agreement. Do not automatically treat it as cash received or a refund transaction.", "aliases": [], "search_keywords": [], "formula": "", "technical": "", "origin": "reference", "needs_decision": false, "section": "B2B invoicing", "entity": "billing_adjustment", "type": "definition", "related": [], "pending_decision_ids": [] }, { "name": "Commitment Fee", "definition": "An onboarding fee associated with confirming a handover reservation.", "note": "Often called booking fee, but labels overlap with “deposit” in PRDs and mobile screens. No universal amount or refund promise follows from the label.", "aliases": [ "CF" ], "formula": "", "technical": "Identify charge purpose and stage using BillingDetailTypeEnum: COMMITMENT_FEE, DEPOSIT, BILLING, ADDITIONAL_FEE, REFUND, GENERAL. PRDs conflict on naming, timing, and refundability; mobile deposit copy says non-refundable while some PRDs allow a refund. The type code identifies the charge, not its refund policy.", "origin": "reference", "section": "Onboarding payments", "id": "payment-commitment-fee", "related": [ "payment-deposit", "application-handover-pending" ], "type": "definition", "needs_decision": true, "entity": "payment", "search_keywords": [ "tanda jadi", "Deposit 1st term", "Booking fee", "deposit 1st term" ], "pending_decision_ids": [] }, { "id": "payment-deposit", "name": "Deposit", "definition": "An upfront customer payment recorded separately from the booking or commitment fee and recurring installments.", "note": "Deposit, DP, and booking-fee labels vary by source. Identify the exact charge type, program, and stage before applying refund or deduction terms.", "aliases": [], "search_keywords": [ "DP", "down payment", "uang muka", "uang jaminan", "Deposit 2nd term" ], "formula": "", "technical": "Identify charge purpose and stage using BillingDetailTypeEnum: COMMITMENT_FEE, DEPOSIT, BILLING, ADDITIONAL_FEE, REFUND, GENERAL. PRDs conflict on naming, timing, and refundability; mobile deposit copy says non-refundable while some PRDs allow a refund. The type code identifies the charge, not its refund policy.", "origin": "reference", "needs_decision": true, "section": "Onboarding payments", "entity": "payment", "type": "definition", "related": [ "payment-commitment-fee", "payment-initial-paid-billing", "contract-b2c-rto-program-completion" ], "pending_decision_ids": [] }, { "name": "Free Billing", "definition": "Promotional treatment that waives eligible installment charges.", "note": "Additional fees may remain due. Credit Connect’s first-sequence complimentary billing follows a separate rule.", "aliases": [], "formula": "", "technical": "", "origin": "reference", "section": "Billing & fees", "id": "payment-free-billing", "related": [ "payment-initial-paid-billing", "payment-hold-billing" ], "type": "definition", "needs_decision": false, "entity": "payment", "search_keywords": [ "Complimentary billing", "FREE_BILLING" ], "pending_decision_ids": [] }, { "name": "Initial-Paid Billing", "definition": "A program’s initial installment allowance used to cover eligible bills without a new payment on each billing date.", "note": "Separate from promotional free billing and Credit Connect’s first-sequence complimentary rule.", "aliases": [], "formula": "", "technical": "", "origin": "reference", "section": "Billing & fees", "id": "payment-initial-paid-billing", "related": [ "payment-free-billing", "payment-deposit" ], "type": "definition", "needs_decision": false, "entity": "payment", "search_keywords": [], "pending_decision_ids": [] }, { "id": "payment-hold-billing", "name": "Hold Billing", "definition": "A temporary hold on regular installment billing for a specified period.", "note": "The Done PRD calls for DPD to stay at its pre-hold value. That is documented intent, not proof of every code path. A hold is not repayment or an arrears waiver.", "aliases": [ "Tunda Bayar", "Libur Bayar" ], "search_keywords": [ "billing hold", "HOLD_BILLING", "ON_HOLD" ], "formula": "", "technical": "PRD 658276353 specifies a DPD freeze. Pinned billing code treats ON_HOLD as a hard hold and REQUESTED/APPROVED windows as soft holds. Hard hold wins over program free billing; program free billing wins over soft hold. Request statuses are REQUESTED, APPROVED, ON_HOLD, REJECTED, COMPLETED, EXPIRED, CANCELLED. A submitted request is not the same as an active hold; confirm the effective window and DPD calculation.", "origin": "reference", "needs_decision": true, "section": "Billing & fees", "entity": "billing", "type": "definition", "related": [ "payment-stop-billing", "payment-stop-accrual", "payment-dpd" ], "pending_decision_ids": [] }, { "name": "Late Bill Count", "definition": "The number of unpaid bills that are at least one day overdue.", "note": "Count each bill once while a due balance remains, including partial payments. One bill overdue four days is still one bill. First-late-day timing varies by source.", "aliases": [ "Overdue bill count" ], "formula": "", "technical": "Pinned Credit Connect counts unpaid rows with per-bill DPD ≥1. PRD 385744907 shifts the first late day to H+2; do not silently apply that delay to every report.", "origin": "reference", "section": "Delinquency", "id": "payment-late-bill-count", "related": [ "payment-dpd", "contract-recorded-default" ], "type": "definition", "needs_decision": true, "entity": "payment", "search_keywords": [], "pending_decision_ids": [] }, { "id": "payment-dpd", "name": "DPD (Calendar Days)", "definition": "Calendar days since the oldest due date with an unpaid overdue balance, measured at the reporting date; minimum 0.", "note": "DPD is 0 when nothing is overdue. Partial payment stays overdue while a due balance remains. Reconstruct balances and allocations at the historical cutoff. Hold-adjusted values and billing-cycle counts are different measures.", "aliases": [ "Days Past Due", "Calendar DPD" ], "search_keywords": [ "DPD", "H+2", "first late day" ], "formula": "max(0, reporting date − oldest unpaid due date); 0 if no overdue balance", "technical": "The pinned Credit Connect helper computes per-bill calendar aging and separately counts late bills. Other PRDs increment DPD per missed cycle or start the first late day at H+2; neither is a universal calendar-day rule. Read hold treatment and source basis before comparing values.", "origin": "reference", "needs_decision": true, "section": "Delinquency", "entity": "contract_payment", "type": "definition", "related": [ "payment-arrears", "payment-late-bill-count", "payment-legacy-dpd-label", "payment-hold-billing", "payment-default" ], "pending_decision_ids": [] }, { "id": "payment-billing", "name": "Billing", "definition": "A record of an amount due, its due date, and payment status.", "note": "Payments and allocations are separate transactions. A bill can receive several partial payments; payment date does not replace due date.", "formula": "", "technical": "", "aliases": [], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Billing & payment timing", "entity": "bill", "type": "definition", "related": [ "payment-chargeable-billing", "payment-settled-billing", "payment-dpd" ], "pending_decision_ids": [] }, { "id": "payment-default", "name": "Default (Reporting)", "definition": "A contract classified as DEFAULT in the specified reporting snapshot.", "note": "State the snapshot and its bucket rules. Calendar DPD ≥4 is a separate glossary convention; it is not a verified equivalent of the dashboard bucket. Default alone does not establish idle or stopped billing.", "formula": "", "technical": "Dashboard K01 selects dpd_bucket from l1.contract_dpd_snapshot; its query metadata defines DEFAULT as 4+ consecutive unpaid daily billing cycles. K01 does not calculate calendar DPD. PRDs instead describe DPD >2 or 120-hour thresholds; do not harmonize them without a policy decision.", "aliases": [ "Reporting Default" ], "search_keywords": [], "origin": "reference", "needs_decision": true, "section": "Delinquency", "entity": "contract", "type": "definition", "related": [ "payment-dpd", "payment-legacy-dpd-label", "contract-recorded-default", "payment-late-bill-count" ], "pending_decision_ids": [] }, { "id": "payment-stop-billing", "name": "Stop Billing", "definition": "Suspension or cessation of creating new customer charges from an effective date.", "note": "Existing debt remains unless separately settled or adjusted. Default or recovery does not imply billing has stopped; use the actual schedule and effective stop or hold.", "formula": "", "technical": "", "aliases": [], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Billing controls", "entity": "bill", "type": "definition", "related": [ "payment-hold-billing", "payment-stop-accrual", "payment-outstanding-balance" ], "pending_decision_ids": [] }, { "id": "payment-stop-accrual", "name": "Stop Accrual", "definition": "Suspension of accounting revenue recognition under the applicable accounting policy.", "note": "This is separate from creating bills and receiving cash. No automatic Default threshold or accounting policy is established by this glossary.", "formula": "", "technical": "", "aliases": [], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Billing controls", "entity": "accounting_policy", "type": "definition", "related": [ "payment-stop-billing", "payment-cash-received", "payment-chargeable-billing" ], "pending_decision_ids": [] }, { "id": "payment-legacy-dpd-label", "name": "Legacy DPD Labels", "definition": "Source-provided delinquency labels such as DPD 1–3, Near Default 1/2, and Default.", "note": "They are categorical labels; do not convert them into calendar days or current snapshot buckets without a verified mapping.", "technical": "Legacy dbt summaries select the latest payment_order label rather than recalculating elapsed days. PRDs describe missed cycles, an H+2 first late day, or hour-based thresholds; these are distinct bases.", "formula": "", "aliases": [], "search_keywords": [], "entity": "delinquency_measure", "section": "Delinquency", "origin": "reference", "needs_decision": true, "type": "definition", "related": [ "payment-dpd", "payment-default" ], "pending_decision_ids": [] }, { "id": "payment-billing-health", "name": "Contract Billing Status", "definition": "A contract’s billing-health field, separate from its lifecycle and individual bill payments.", "note": "Recorded values are NORMAL, LATE, SUSPENDED, and COMPLETED. SUSPENDED does not by itself establish contract termination.", "technical": "BillingStatus belongs to CustomerContract. This field is distinct from CustomerContractStatus and from BillingPaymentStatusEnum on an individual bill; a screen label is not a substitute for the backend field.", "formula": "", "aliases": [], "search_keywords": [], "entity": "contract", "section": "Billing status", "origin": "current", "needs_decision": false, "type": "status", "related": [], "pending_decision_ids": [] }, { "id": "payment-bill-payment-status", "name": "Bill Payment Status", "definition": "The recorded settlement state of an individual bill.", "note": "UNPAID, PROCESSING, and PARTIAL_PAID remain distinct from PAID. A failed payment attempt does not prove that the bill is settled.", "technical": "BillingPaymentStatusEnum includes UNPAID, PAID, PROCESSING, PARTIAL_PAID and legacy FAILED (deprecated in the schema). Gateway/transaction attempts have separate states. Do not recode historical FAILED records solely from deprecation comments or a mobile display label.", "formula": "", "aliases": [], "search_keywords": [], "entity": "bill", "section": "Billing status", "origin": "current", "needs_decision": false, "type": "status", "related": [], "pending_decision_ids": [] } ] }, { "id": "fleet", "title": "Fleet performance", "description": "One reporting cutoff, one vehicle population, and an explicit billing proxy.", "terms": [ { "id": "fleet-eligible-fleet", "name": "Eligible Fleet", "definition": "Vehicles in the declared reporting scope with a confirmed customer handover on or before the cutoff, excluding paid-off vehicles.", "note": "Use unique vehicles and states effective at the cutoff. Declare treatment of disposed, written-off, and missing units; paid-off exclusion alone does not resolve fleet scope. Unknown exit mapping is a coverage gap, not zero.", "formula": "Eligible Fleet = Earning Eligible Vehicles + Previously-Handed-Over Idle", "technical": "Dashboard V03 counts in-scope B2C vehicles with known cutoff status other than PAID_OFF and a first deployment date. This is a reporting population, not proof of legal ownership. WRITTEN OFF appears in PRD 571637763 but not in the pinned VehicleStatusEnum.", "aliases": [], "search_keywords": [], "origin": "reference", "needs_decision": true, "section": "Fleet scope", "entity": "vehicle", "type": "definition", "related": [ "fleet-earning-vehicle", "fleet-previously-handed-idle", "vehicle-vehicle-paid-off" ], "pending_decision_ids": [] }, { "id": "fleet-earning-vehicle", "name": "Earning Eligible Vehicles", "definition": "Eligible vehicles meeting the declared billing-based earning rule at the reporting cutoff.", "note": "Declare the billing window, operational-state rule, and Default treatment. Billing on the report date is a daily convention; a trailing seven-day numerator measures a different window. Neither is cash received or accounting revenue.", "formula": "", "technical": "Dashboard V03 requires ACTIVE at cutoff (using vehicle audit history when needed), prior customer handover, positive chargeable billing dated cutoff minus six days through cutoff, and a linked cutoff snapshot whose bucket is not DEFAULT. These filters differ from the glossary’s earlier report-date-only convention; a lookup window can retain vehicles whose earning has since stopped.", "aliases": [ "Earning Vehicle" ], "search_keywords": [], "origin": "reference", "needs_decision": true, "section": "Earning & utilization", "entity": "vehicle", "type": "definition", "related": [ "fleet-eligible-fleet", "payment-chargeable-billing", "payment-cash-received", "payment-stop-accrual" ], "pending_decision_ids": [] }, { "id": "fleet-utilization", "name": "Eligible-Fleet Utilization", "definition": "Earning eligible vehicles divided by eligible fleet at the same reporting cutoff.", "note": "Use the same scope, unique vehicles, and earning rule on both sides. Never-handed-over stock is outside this denominator. Zero denominator or incomplete coverage means unavailable.", "formula": "Earning Eligible Vehicles ÷ Eligible Fleet × 100%", "technical": "Dashboard V03 divides revenue_active_units by handed_over_owned_units, not the ACTIVE-only utilization_base_units. Its numerator is ACTIVE, seven-day billed, and non-DEFAULT on the snapshot; the registry labels that definition Agreed. An owned-fleet ratio has a different denominator.", "aliases": [ "Utilization" ], "search_keywords": [], "origin": "reference", "needs_decision": true, "section": "Earning & utilization", "entity": "vehicle", "type": "definition", "related": [ "fleet-eligible-fleet", "fleet-earning-vehicle", "fleet-idle" ], "pending_decision_ids": [] }, { "id": "fleet-idle", "name": "Total Idle", "definition": "Non-paid-off vehicles in the declared reporting scope that do not meet the billing-based earning rule at the cutoff.", "note": "Includes never-handed-over and previously-handed-over vehicles under one earning rule. Declare disposal, write-off, and missing-unit treatment. Unknown billing or exit coverage is unavailable, not automatically idle or zero.", "formula": "Total Idle = Never-Handed-Over Idle + Previously-Handed-Over Idle", "technical": "", "aliases": [ "Idle" ], "search_keywords": [], "origin": "reference", "needs_decision": true, "section": "Idle population", "entity": "vehicle", "type": "definition", "related": [ "fleet-never-handed-idle", "fleet-previously-handed-idle", "fleet-earning-vehicle" ], "pending_decision_ids": [] }, { "id": "fleet-never-handed-idle", "name": "Never-Handed-Over Idle", "definition": "Idle vehicles with no confirmed customer handover on or before the reporting cutoff.", "note": "Exclude paid-off vehicles. Warehouse or city transfers are not customer handovers. Count each vehicle once.", "formula": "", "technical": "", "aliases": [ "Never-Handed Idle" ], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Idle population", "entity": "vehicle", "type": "definition", "related": [ "fleet-idle", "handover-physical-handover" ], "pending_decision_ids": [] }, { "id": "fleet-previously-handed-idle", "name": "Previously-Handed-Over Idle", "definition": "Eligible vehicles not earning under the billing-based rule on the reporting date.", "note": "Exclude paid-off vehicles and apply the same fleet scope, cutoff, and earning window as the numerator. Count each vehicle once; never subtract total idle from eligible fleet.", "formula": "Eligible Fleet − Earning Eligible Vehicles", "technical": "", "aliases": [ "Previously-Handed Idle" ], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Idle population", "entity": "vehicle", "type": "definition", "related": [ "fleet-idle", "fleet-eligible-fleet", "fleet-earning-vehicle" ], "pending_decision_ids": [] }, { "id": "fleet-idle-duration", "name": "Idle Duration", "definition": "Elapsed idle time measured with a stated start event and end event or reporting cutoff.", "note": "Total downtime may include recovery, repair, and QC. Ready-to-rent waiting time starts only when readiness is confirmed. State clocks and targets separately for never-handed-over and previously-handed-over vehicles.", "formula": "", "technical": "", "aliases": [], "search_keywords": [], "origin": "reference", "needs_decision": false, "section": "Idle time", "entity": "vehicle", "type": "definition", "related": [ "fleet-never-handed-idle", "fleet-previously-handed-idle", "vehicle-ready-to-handover", "vehicle-in-repair" ], "pending_decision_ids": [] } ] } ], "decisions": [], "resolutions": [ { "id": "business-model-taxonomy", "decided_on": "2026-10-27", "authority": "user", "summary": "B2B2C is the newer business model. RF is a program under B2B2C; main models remain B2B, B2C, B2B2C." }, { "id": "sale-and-leaseback-scope", "decided_on": "2026-10-27", "authority": "user", "summary": "S&L requires leasing purchased assets back to the same seller. Ordinary OEM procurement for B2B rental or B2C RTO is separate." } ], "manifest": { "term_count": 77, "topic_count": 9, "decision_count": 0, "needs_decision_count": 29, "content_hash_scope": "payload excluding manifest", "content_sha256": "e48a7f646ff779087db20b325fd440c70ec013ad083af26b4908ee47a663c0ee" } }