Field Service
Interventions sur site
À quoi elle sert
Schedule on-site jobs for customers: who does the work, where, when, which parts were used and whether the customer must sign off. Site addresses and contacts are personal data and treated as such.
Ce que fait et ne fait pas le paquet
On-site jobs for customers, done by a technician: scheduled, en route, in progress, done or cancelled. A job records the customer, the site, the technician, the planned day and start (minutes since midnight), the parts used and whether the customer must sign off. Site address and contact details are personal data. Needs the Human Resources and Products packages.
Modèles
field_service_job
An on-site job for a customer
Groupe de lecture: field_service.user. Groupe d'écriture: field_service.user.
| Champ | Type | Classe de données | Données personnelles | Groupe | Vu par les agents | Description |
|---|---|---|---|---|---|---|
name | text | none | non | field_service.user | en clair | Short title of the job, for example Replace boiler pump |
customer_id | ref → party | none | non | field_service.user | en clair | The customer the job is for |
site_name | text | none | non | field_service.user | en clair | Name of the site, for example Main warehouse |
site_address | longtext | internal | oui | field_service.user | masqué | Street address where the work is done; often a person's home |
site_city | text | internal | oui | field_service.user | masqué | City of the site |
site_postcode | text | internal | oui | field_service.user | masqué | Postcode of the site |
site_country | text | none | non | field_service.user | en clair | Country of the site |
site_contact_name | text | internal | oui | field_service.user | masqué | Name of the person to meet on site |
site_contact_phone | text | internal | oui | field_service.user | masqué | Phone number of the person to meet on site |
technician_id | ref → hr_employee | internal | oui | field_service.user | masqué | Technician assigned to the job |
priority | select (low, normal, high, urgent) | none | non | field_service.user | en clair | How urgent the job is: low, normal, high, urgent |
description | longtext | none | non | field_service.user | en clair | What has to be done and what the customer reported |
scheduled_on | date | none | non | field_service.user | en clair | Planned day of the visit (YYYY-MM-DD) |
scheduled_start_minute | number | none | non | field_service.user | en clair | Planned start in minutes since midnight (540 is 09:00) |
planned_minutes | number | none | non | field_service.user | en clair | Planned duration in minutes |
signature_required | bool | none | non | field_service.user | en clair | Whether the customer has to sign off the work before it counts as done |
signed_by | text | internal | oui | field_service.user | masqué | Name of the person who signed off the work |
signed_on | date | none | non | field_service.user | en clair | Day the customer signed off (YYYY-MM-DD) |
work_report | longtext | none | non | field_service.user | en clair | What was done, written by the technician |
state | select (scheduled, en_route, in_progress, done, cancelled) | none | non | field_service.user | en clair | Job status: scheduled, en_route, in_progress, done, cancelled |
field_service_part
A part or product used on a job
Groupe de lecture: field_service.user. Groupe d'écriture: field_service.user.
| Champ | Type | Classe de données | Données personnelles | Groupe | Vu par les agents | Description |
|---|---|---|---|---|---|---|
job_id | ref → field_service_job | none | non | field_service.user | en clair | The job the part was used on |
product_id | ref → product | none | non | field_service.user | en clair | The product that was used |
quantity | number | none | non | field_service.user | en clair | How many units were used |
unit_price | money | none | non | field_service.user | en clair | Price per unit charged to the customer (minor currency units, e.g. cents) |
note | text | none | non | field_service.user | en clair | Remark about the part, for example serial number |
Flux de travail
field_service_job
| Action | Transition | Qui peut l'exécuter | Approbation |
|---|---|---|---|
field_service_job.depart | state: scheduled → en_route | field_service.user | non |
field_service_job.start | state: en_route → in_progress | field_service.user | non |
field_service_job.complete | state: in_progress → done | field_service.user | non |
field_service_job.cancel | state: scheduled → cancelled | field_service.manager | non |
Groupes de permissions
Groupes utilisés par cette application :
field_service.managerfield_service.user
Étapes d'approbation
Aucune étape de cette application ne requiert d'approbation, hormis la suppression d'enregistrements.
Ce que les agents peuvent et ne peuvent pas faire
Un agent peut lire, rechercher, créer et modifier les enregistrements de cette application, et exécuter les actions qui ne requièrent pas d'approbation, dans les limites des groupes de permissions de son jeton.
Il ne peut que proposer ces étapes, qu'une personne doit approuver : field_service_job.delete, field_service_part.delete.
Les données personnelles sont masquées sous forme de jetons de substitution : field_service_job.site_address, field_service_job.site_city, field_service_job.site_postcode, field_service_job.site_contact_name, field_service_job.site_contact_phone, field_service_job.technician_id, field_service_job.signed_by.
Dépendances
baseproducthr
Installation
Installez-la depuis l'application Customize (Place de marché), ou en ligne de commande :
obop modules install-from field_serviceNécessite une base de données et des droits d'administrateur.
Créer la vôtre
Le guide des modules montre comment sont écrites les applications de ce type