Asset Management Scope and Capabilities

Summary

Capability maturity is based on executable source, not labels or roadmap expectations.

Audience

Business owners, product, architecture, engineering, QA, support, and implementation teams.

Reference Content

Classification	Capabilities
Implemented	Asset records; tenant-scoped inventory; request; assign; return; mark available; damage; loss; retirement; history; document references and content handoff; audit/timeline; lifecycle outbox events; open-asset clearance checks
Partial	Type governance is free text; list filters are limited; employee association is identifier-only; approval exists but is configuration-dependent; repair exists only as a recognized status/condition and clearance blocker
Transitional	Compatibility-shaped HR Operations routes/UI, legacy-compatible identity, and source-derived dashboard metrics coexist with dedicated service endpoints
Foundation	Dedicated service identifies its stage as Foundation; future technical/API/database/events/UI/operations/reference sections are landing pages only in this epic
Not implemented	Categories/hierarchy, transfer, reservation, maintenance or repair work orders, warranty/service records, vendors/purchases/cost, locations/departments, theft-specific flow, recovery/replacement, disposal, depreciation, procurement, payroll/finance recovery

Import/export controls exist in the HR Operations UI, including bulk import presentation, but no dedicated domain-level bulk command or export report was verified. Treat this as Transitional UI behavior.

Related Articles

• Business overview
• Known limitations

See Also

• Business rules
• Dashboard and reports

Keywords

• Capability maturity
• Asset scope

Revision Information

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

Source References

• microservices/src/asset-service/Api/AssetEndpoints.cs
• microservices/src/asset-service/Application/Commands/AssetCommands.cs
• UI/salary-ui/apps/client-hrms-portal/src/dashboard/DashboardPages.tsx