Asset Management

Entry: /assets. Assets owns serial identity, Asset Tags, Device Models, firmware notes and lifecycle. Have the correct Group, model and serial information ready. Catalog management, Asset creation, receiving and lifecycle actions can require different permissions; Procurement and Facilities information is an authorized projection from those owners.

Register equipment

1. Open Catalogs and confirm that the intended Category and Device Model are available. Ask the catalog owner to register missing model information instead of selecting an unrelated model.
2. Open Inventory and choose Register Asset. The owning Group comes from your current authorized context.
3. Select the Category and registered Model, then enter the serial and other applicable Asset fields. Asset Tag is optional; if entered, it must contain one to nine digits and be globally unique.
4. Submit and open the Asset detail. Verify the serial, model and lifecycle before making physical or Network associations.

Accept delivered equipment

1. Open the available Asset receiving workflow for an eligible received Purchase Order line. Check its Agreement, Delivery Note and delivered serials.
2. Use receiving Settings to choose Register New Asset or Link Existing Asset. Register when the delivered unit has no Asset; link only when the selected Asset is that same unit.
3. Review the unit's serial and procurement package, then choose Register Delivered Asset or Link Delivered Asset.
4. Verify the resulting Asset and Procurement relationship. If a request failed, use its reviewed retry after checking the result instead of accepting the unit twice.

Maintain identity and lifecycle

1. Find the Asset in Inventory using search or filters. Use Columns for a relevant view and Export CSV for the authorized selected information.
2. Open the row's Settings for permitted maintenance, such as firmware/note changes or the supported lifecycle transition. Review the exact identity before confirming.
3. For a physical replacement, use the dedicated RMA workflow when available so the old and replacement identities remain traceable. Record physical placement in Facilities and node membership in Network separately.

Blockers and limits: unavailable model choices, duplicate identity, incompatible Asset Type, an incomplete procurement package or retained relationships can prevent a change. Read-only mode prevents mutation. Bulk Asset actions accept up to 250 selected Assets; review batch outcomes. Selection and export scope matter—visible columns do not necessarily remove active filters. Virtual and License Assets do not have physical Rack Units or hardware placement. Missing peer access is shown as restricted or unavailable, not as permission to edit that owner's data.