ILOVA 6.SERVIS VA TEXNIK XIZMAT JARAYONI (Helpdesk & Field Service) ODOO MODULLARI VA ICHKI MODELLAR ARXITEKTURASI

5️⃣ SERVIS VA TEXNIK XIZMAT JARAYONI

(Helpdesk & Field Service)

ODOO MODULLARI VA ICHKI MODELLAR ARXITEKTURASI

(ISO 13485:2016 – Audit Ready)

1️⃣ ARXITEKTURA YONDASHUVI (PRINSIPLAR)

✅ Faqat Odoo Enterprise standard modullari

❌ Custom modul yo‘q (faqat konfiguratsiya)

✅ Traceability (Serial / Lot → Service → CAPA)

✅ Audit trail & records (Documents + Chatter)

✅ KPI → Payroll avtomatik

✅ Servis → Ombor → Accounting → Quality uzluksiz zanjir

2️⃣ ISHLATILADIGAN ODOO MODULLARI (CORE)

📌 Izoh: “Zapchast” → Ehtiyot qismlar,

“Rasxod materiallar” → Sarflanadigan materiallar

3️⃣ ASOSIY DATA MODELLAR (ICHKI OBYEKTLAR)

3.1. Helpdesk Ticket

Model: helpdesk.ticket

Majburiy maydonlar:

• Ticket ID (auto)

• Customer (res.partner)

• Product (serial / lot majburiy)

• Warranty Status (Warranty / Non-warranty)

• Issue Type (Nosozlik / Sozlash / Profilaktika)

• Priority (Low / Medium / High / Critical)

• SLA Deadline

• Assigned Engineer

• Status:

  New → In Progress → Waiting Parts → Done → Closed

📌 ISO 13485: 8.2.1 (Customer Feedback)

3.2. Field Service Task

Model: project.task (Field Service)

Bog‘lanish:

• Helpdesk Ticket ↔ Field Service Task (1:1)

Maydonlar:

• Work Start / End Time

• Location (Customer site)

• Used spare parts

• Work Result

• Customer Signature (Service Act)

📌 ISO: 7.5.1 (Service Provision)

3.3. Inventory — Ehtiyot qismlar & Sarflanadigan materiallar

Model: stock.move, stock.move.line

Qoidalar:

• Har bir servis task → material chiqimi

• Serial / Lot majburiy

• Ombordan avtomatik kamayish

• Qaysi ticket / taskga ketgani traceable

📌 ISO: 7.5.3 (Identification & Traceability)

3.4. Sales & Accounting (Pullik servis)

Model: sale.order, account.move

Logika:

• Agar Warranty = No → Sales Order ochiladi

• SO → Invoice (draft)

• Invoice → 1C ga uzatiladi

• Bepul servis → Approval talab qilinadi

📌 ISO: 7.2.2 (Contract Review)

3.5. Documents (DMS)

Model: documents.document

Saqlanadigan hujjatlar:

• Servis akti

• Texnik xulosa

• Foto / video dalillar

• Mijoz tasdig‘i

Papka struktura:

Documents

└── Master documents

    └── Service

        ├── Service Acts

        ├── Technical Reports

        ├── Photos & Videos

3.6. Quality & CAPA integratsiyasi

Trigger:

• Issue Type = “Nosozlik”

• Yoki takroriy servis (Repeat Failure)

Oqim:

Helpdesk Ticket

   ↓

Quality Alert

   ↓

CAPA

4️⃣ TO-BE SERVIS JARAYONI (END-TO-END FLOW)

Mijoz murojaati

   ↓

Helpdesk Ticket

   ↓

Warranty tekshiruvi (Approvals)

   ↓

Field Service Task

   ↓

Ehtiyot qismlar chiqimi (Inventory)

   ↓

Service Act (Documents)

   ↓

Sales Order (agar pullik)

   ↓

Invoice → 1C

   ↓

Ticket yopiladi

   ↓

Nosozlik bo‘lsa → Quality → CAPA

5️⃣ KPI & PAYROLL INTEGRATSIYASI

5.1. Servis KPI’lar

5.2. Payroll bog‘lanishi

Formula:Oylik = Base salary

      + SLA bonus

      + On-time closure bonus

      − Repeat failure penalty

📌 Odoo:

• KPI → HR → Payroll Rules

• Bonus avtomatik hisoblanadi

6️⃣ RBAC — ROLLAR & HUQUQLAR