Skip to main content

Asset Terminology

Summary

This glossary defines the vocabulary of Asset Management, deliberately separating terms by the layer they belong to. The same concept can carry a domain name, a user-facing label, a compatibility name, an integration name, and a persistence name; keeping these distinct prevents confusion when moving between the aggregate, the UI, the monolith-shaped surface, the event contracts, and the database.

Audience

Developers, QA engineers, support engineers, solution architects, and implementation partners who need a shared, precise vocabulary when reading the other reference pages or the authoritative documentation.

Reference Content

Domain terms

TermMeaning
Asset (aggregate root)The consistency boundary for a tracked asset and its lifecycle.
AssetStatusThe lifecycle state; one of ten values (see Status Reference).
AssetConditionThe physical condition; one of five values (New, Good, Repair, Damaged, Lost).
Assignment historyAggregate child recording who an asset was assigned to over time.
Document referenceAggregate child pointing to bytes held in the document service.
Value objectA validated-on-construction wrapper for code, name, serial, or assignee.
Domain eventAn in-process signal (six exist) raised on a lifecycle transition.

UI label terms

TermMeaning
Asset RequestsThe admin tab label under HR Operations.
My Assets (ESS)The employee self-service asset view.
Nav key asset-requestsNavigation identifier for the admin view.
Nav key ess-assetsNavigation identifier for the employee view.
Module feature hr-operationsThe feature gate governing admin visibility.

Compatibility terms

TermMeaning
Compatibility surfaceMonolith-shaped endpoints that mirror the legacy HR Operations shape.
CompatIdA numeric identity used to reconcile with legacy records; may be 0 at create.
Compatibility approve/rejectCompatibility actions that set Issued and Rejected respectively.

Integration terms

TermMeaning
Lifecycle eventAn integration contract (six exist) published to the event bus.
AssetLifecycleDataThe uniform shared payload type carried by all six contracts.
OutboxThe transactional store-and-relay mechanism for events.
Workflow callbackThe idempotent inbound call that advances a managed request.

Persistence terms

TermMeaning
Schema assetThe dedicated PostgreSQL schema for the service.
Tenant query filterAn EF global filter applied per tenant at the application layer.
ProcessedEventsThe store used for inbound idempotency.
OutboxMessagesThe persisted outbound event queue.

Source References

  • microservices/src/asset-service/Domain/Common/Enums.cs
  • microservices/src/asset-service/Domain/Common/ValueObjects.cs
  • microservices/src/asset-service/Domain/Asset/Asset.cs
  • microservices/src/asset-service/Api/AssetCompatEndpoints.cs

See Also

Keywords

asset terminology, glossary, domain terms, compatibility, integration terms

Revision Information

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly