📄 ILOVA 2. ODOO MODULLARI VA ICHKI MODULLAR ARXITEKTURASI SIFAT BOSHQARUVI JARAYONI

ILOVA 2. ODOO MODULLARI VA ICHKI MODULLAR ARXITEKTURASI SIFAT BOSHQARUVI JARAYONI

1) Modul to‘plami (QMS Scope)

  1. Quality (asosiy QMS: NC/CAPA/Checks)

  2. Helpdesk (Complaint manbasi, SLA)

  3. Project (CAPA Action Plan – tasklar)

  4. Documents (Quality Manual/SOP/Records + versioning)

  5. Approvals (Policy/Audit/CAPA tasdiqlash)

  6. Employees (rol/bo‘lim/mas’ullar)

  7. Spreadsheet / Dashboards (KPI monitoring)

  8. Discuss / Chatter / Activities (audit trail, ichki yozishmalar, follow-up)

2) Har bir modul ichidagi STANDARD ichki modellar (Developer uchun)


2.1. QUALITY (QMS, CAPA, Nonconformity)


Asosiy modellar:

  • quality.alert — Quality Alert / Nonconformity / CAPA “case” sifatida yuritiladi

    • Statuslar: New → Confirmed → Action Plan → Verification → Done (workflow konfiguratsiya)

  • quality.check — Verification / Check (CAPA yopilishidan oldin tekshiruv dalili)

  • quality.point — Quality Control Point (qachon check ishlashi: operatsiya/ombor/ishlab chiqarish nuqtalari)

  • quality.team — Quality Team (QMS guruh / mas’ullar)

  • quality.tag — tasnif/analitika (Complaint/Audit/Risk/Service kabi tag’lar)

  • (agar ishlab chiqarish bo‘lmasa) quality.point va quality.check logika uchun minimal ishlatiladi (Verification bosqichi sifatida).


QMS uchun majburiy field/strukturasi (audit-ready):

  • quality.alert.name (Case ID), company_id, team_id, responsible_id

  • quality.alert.description (RCA: 5Why/Ishikawa matni)

  • quality.alert.tag_ids (turi: Complaint/Audit/Risk/Service)

  • quality.alert.message_ids / chatter (izohlar, audit trail)

  • Attachmentlar: ir.attachment orqali (RCA diagramma, dalil, surat, protokol)

2.2. HELPDESK (Complaints manbasi + SLA)


Asosiy modellar:

  • helpdesk.ticket — Complaint / Issue (manba: Customer/Service/Sales/Logistics)

  • helpdesk.team — Complaint qabul qiluvchi jamoa

  • helpdesk.stage — Ticket stage (New/In Progress/Waiting/Closed)

  • helpdesk.sla — SLA qoidalari (1st response, closure time)

  • helpdesk.ticket.type (agar sizda yoqilgan bo‘lsa) — Ticket Type (Complaint/Service Request)


Bog‘lanish (standard usul):

  • helpdesk.ticket → Quality Alert ochish (amaliyotda 2 yo‘l):

    1. ticketdan “Create Quality Alert” (server action/automated action bilan)

    2. ticket yopilish sharti: Major/Critical bo‘lsa quality.alert majburiy


Bu yerda “custom model” shart emas, Automated Actions + Tags bilan ishlaydi.

2.3. PROJECT (CAPA Action Plan)


Asosiy modellar:

  • project.project — CAPA Action Plan loyihasi (QMS-CAPA)

  • project.task — Corrective/Preventive Action tasklari

  • project.task.type — task stage (To Do / Doing / Done / Verified)

  • project.tags — action type (CA/PA/Training/Doc Update)


Mapping:

  • 1 ta quality.alert (CAPA case) → bir nechta project.task (CA/PA)

  • Tasklarda: mas’ul (user_id), muddati (date_deadline), dalil (attachment) majburiy

2.4. DOCUMENTS (QMS hujjatlar + Records)


Asosiy modellar:

  • documents.document — Quality Manual, SOP, Records, Audit Reports

  • documents.folder — QMS papka strukturasi (QMS/Policy/Manual/SOP/Records/Audit)

  • documents.tag — klassifikatsiya (SOP, Policy, Record, Audit)

  • ir.attachment — hujjat ilovalari (har bir case/ticket/task’ga biriktiriladi)


Audit-ready talablar:

  • Versioning/Revision: documents.document revision mexanizmi (Odoo standard)

  • Access control: folder bo‘yicha ruxsat (groups)

  • Review reminders: Activities (mail.activity) bilan

2.5. APPROVALS (Tasdiqlash)


Asosiy modellar:

  • approval.request — tasdiqlash so‘rovi (Policy Approval, CAPA Closure Approval, Audit Plan Approval)

  • approval.category — approval turlari (QMS Policy, CAPA Close, Audit Plan)

  • approval.approver — approverlar ro‘yxati


Mapping:

  • CAPA yopilishidan oldin: approval.request (“CAPA Close Approval”)

  • Policy/SOP kuchga kirishi: approval.request (“Document Approval”)

2.6. EMPLOYEES (Rollar / mas’ullar)


Asosiy modellar:

  • hr.employee — xodim (Quality Manager, Auditorlar)

  • hr.department — bo‘limlar (SAL-02, SRV-03, REG-05…)

  • hr.job — lavozim (Quality Manager, Auditor, Service Engineer)


RBAC (keyin siz so‘ragan jadval) shu yerga tayanadi.

2.7. KPI: SPREADSHEET / DASHBOARDS


Asosiy modellar:

  • spreadsheet.dashboard / spreadsheet.sheet (Odoo Enterprise) — KPI dashboard

  • Hisobotlar manbasi:

    • Complaints: helpdesk.ticket

    • CAPA/NC: quality.alert

    • Verification: quality.check

    • Action Plan: project.task

    • Documents KPI: documents.document

2.8. AUDIT TRAIL (Discuss/Chatter/Activities)


Asosiy modellar:

  • mail.message — chatter yozishmalari (kim, qachon, nima o‘zgardi)

  • mail.activity — follow-up, review, deadline reminder

  • res.users / res.groups — access tracking


ISO 13485 uchun audit izi shu qatlam bilan yopiladi.

3) End-to-End “zanjirlik” (faqat standard obyektlar bilan)


3.1. Complaint → CAPA oqimi

  1. Complaint keladi: helpdesk.ticket (Type=Complaint, Priority=Major/Critical)

  2. Quality Alert ochiladi: quality.alert (tag=Complaint)

  3. RCA yoziladi: quality.alert.description + attachment (ir.attachment)

  4. Action Plan: project.task lar (CA/PA) → deadline + responsible

  5. Verification: quality.check (pass/fail, evidence)

  6. Approval: approval.request (“CAPA Close Approval”)

  7. Close: quality.alert = Done

  8. KPI: Spreadsheet dashboard (Q1–Q17)


3.2. Audit → Finding → CAPA oqimi (standard ichida)

  • Audit reja/cheklist: documents.document (Audit Plan/Checklist) + project.project (Audit Plan tasks)

  • Finding: quality.alert (tag=Audit)

  • CAPA: o‘sha alert bo‘yicha project.task + quality.check + approval.request


“Audit Module” degan alohida standard modul yo‘q bo‘lishi mumkin; Odoo’da auditni odatda Project + Documents + Quality Alertkombinatsiyasi bilan audit-ready qilinadi.

4) Minimal konfiguratsiya qoidalari (customsiz)

  • Complaint turlari Helpdesk Ticket Type / Tags bilan

  • Quality Alert’da turini Tags (quality.tag) bilan ajratish (Complaint/Audit/Risk/Service)

  • CAPA bosqichlari — quality.alert stage (server actions bilan majburlash: RCA bo‘sh bo‘lsa next stage yo‘q)

  • Verification majburiy: quality.check yaratilmasdan “Done” bo‘lmasin

  • Closure approval majburiy: approval.request bo‘lmasdan “Done” bo‘lmasin