Technician
Select any passage to ask a question about it or to propose replacement wording.
Technician
Part of Nidus Ontology V3 · Relationship Map
Definition
A Technician is a person with the authority and qualifications to carry out the district's operational work: reconnaissance, inspection, treatment, and prevention. They are the accountable actor behind every operational record.
Ontological Position
A real-world entity, represented rather than created by Nidus. The person exists independently of the work they are given, and their identity persists across assignments, routes, seasons, and changes of employment.
A Technician is not a role record or a login. The role is what the person is permitted to do; the Technician is the person who did it, and every record of work names them because accountability does not attach to a work container.
- A Technician may be bound to Routes (Technician |{──o{ Route).
- A Technician executes Assignments (Technician |{──o{ Assignment).
- A Technician makes Observations (Technician ||──o{ Observation).
- A Technician performs Inspections (Technician }o──o{ Inspection).
- A Technician performs Treatments (Technician }o──o{ Treatment).
- A Technician holds the skills that particular work needs (Technician }o──o{ Skill).
- A Technician holds the Certifications that permit particular work (Technician }o──o{ Certification).
- A Technician is issued and accountable for Equipment that stays with them, across assignments and seasons (Technician }o──o{ Equipment).
- A Technician may be annotated by Reviews (Technician ||──o{ Review).
Properties
Identity
- Name — the person's name.
- Organizational affiliation — the district or organization the person works within.
Capability
- Skills — the capabilities the person has, such as species identification or dipping.
- Certifications — the authorizations the person holds, each with an issuing authority and a period of validity. See Certification.
Rules
- An Assignment or Route may involve more than one Technician. Each is accountable for the work they personally performed, and every record names the Technician who made it.
- A Technician's identity persists across assignments, seasons, and any change in their standing with the district. Work already recorded stays attributable to the person who did it.
- A Technician acts within what their certifications permit and their skills make feasible. No record claims more.
- Certification and skill requirements are checked when work is assigned, never applied retroactively to records already made.
Relations
Every relation this concept takes part in is drawn on the relationship map.