D.A.R.C.
D.A.R.C. — the Dealers Accreditation Requirements Checklist — is UAAGI's working file for onboarding a prospective dealer. It is a simple record of (a) the dealership applying, and (b) which of the required documents they have submitted so far.
Internally the feature is the Dealer Dev module inside msd18. Most users just call the whole thing "D.A.R.C." because the checklist is what they open every day.
MSD Administrators, Dealer Dev Managers, and Dealer Dev Users responsible for recruiting and accrediting new dealers.
What it is (and isn't)
It is a document-recording system:
- One record per dealership applying.
- A checklist of up to 16 requirements (LOI, company profile, FBA forms, NDA, etc.).
- For each requirement: a submitted flag, a date, remarks, and the PDF document(s) uploaded.
- A compliance percentage computed from how many active requirements are ticked as submitted.
- An application status (Processing / Approved / Denied / Revoked).
It is not a workflow engine. There are no automatic routing, no approval chains, no notifications. When a document arrives, UAAGI opens the partner record, ticks the checkbox, attaches the file, and saves. The status buttons (Approve / Deny / Revoke / Re-process) are manual buttons UAAGI clicks once a decision is made.
The four things you see in the menu
Dealer Dev (top-level menu) is split into:
| Menu | Model | Purpose |
|---|---|---|
| Dealership | res.partner (with dealer_application=True) | Every dealership application record. |
| Configuration ▸ Dealers Accreditation Requirement | dealers.accreditation.requirements | The master list of up to 16 required documents. Ordered by sequence; inactive = no longer required. |
| Configuration ▸ Brands & Departments | brand, brand.department | The UAAGI brand catalog plus brand-level ONe System integration details. |
Data model
┌───────────────────────────────┐
│ res.partner │
│ (dealer_application = True) │
│ │
│ • brand_id │
│ • dealer_alias │
│ • application_state │
│ • dar_compliance_percentage │
└──────────────┬─────────────────┘
│ One2many (darc_ids)
▼
┌───────────────────────────────────────────────┐
│ dealers.accreditation.requirements.checklist │
│ (DARC entry — one per (partner, requirement)) │
│ │
│ • dar_id ─────► dealers.accreditation. │
│ • submitted requirements (DAR) │
│ • date │
│ • remarks │
│ • darc_file_ids │
└──────────────┬────────────────────────────────┘
│ One2many
▼
┌────────────────────────────────────────────────────┐
│ dealers.accreditation.requirements.checklist. │
│ document │
│ │
│ • name │
│ • doc_file (Binary, rendered as PDF viewer) │
└────────────────────────────────────────────────────┘
A DARC checklist row is auto-created the first time a dealer record is opened or the compliance percentage is recomputed — so the HR team doesn't add rows manually; the 16 requirements appear the moment the partner form loads. See Dealership Applications — how the checklist fills itself for the exact mechanism.
Security groups
Three groups, each granting visibility and edit rights on the Dealer Dev menu:
| Group | Typical assignee |
|---|---|
| MSD Administrators | MSD (IT department) — full control across all MSD-maintained modules |
| Dealer Dev Manager | UAAGI Dealer Development team leads (can edit requirements and brands) |
| Dealer Dev User | UAAGI Dealer Dev staff who record submissions but don't configure the requirements master |
All three groups can see the Dealership menu. Only Administrators and Managers see Configuration.
Guides
- Dealership Applications — create and maintain a dealership record, tick off submitted documents, set status.
- DARC Requirements — maintain the master list of required documents, ordering, and active flag.
- Brands & Departments — UAAGI brand catalog and ONe System integration fields.