Equipment and Activity Model
Equipment is the asset. An activity is work performed on it. Keep them connected so a single equipment record can show its cleaning, calibration, and maintenance history.
How the model connects
An activity refers to the equipment it concerns and, where required, the exact procedure revision used. Its evidence stays with the activity.
Equipment: one shared identity
| Part | Example |
|---|---|
| Identity | Code, name, description |
| Facets | Physical profile, location, governance |
| Relationships | Area, room, category |
| Lifecycle | Draft → Active → Retired |
| Actions | Activate, retire, update profile, link document |
Equipment answers what is this asset, where is it, and can it be used? Its identity remains the same across the activities performed on it.
Activity: one occurrence of work
| Part | Example |
|---|---|
| Identity | Activity number and type |
| Relationships | Equipment, performer, procedure revision |
| Fields | Readings, result, comments |
| Evidence | Checklist, photo, signature |
| Actions | Start, complete, review, reject |
Activity answers who did what, when, and with which evidence? Create an activity entity when the work needs its own record, assignment, review, or reporting.
This is an example lifecycle. Define the transitions your process allows. Completion can require readings and evidence; review can require a different authorized person.
Extend equipment without copying it
Different features can contribute facets to the same equipment entity through descriptors.
Cleaning and calibration can each keep their own activity records while contributing the details users need on the equipment record. They share equipment identity rather than maintaining separate asset lists.
Put it into practice
- Declare equipment and its core facets.
- Declare the activity entity and its relationships.
- Add actions, lifecycle transitions, permissions, and evidence requirements.
- Contribute additional equipment facets as features grow.
- Use views to show equipment details alongside its activity history.
Continue with facets and entities, actions and lifecycles, or modules and contributions.