Asset & supplier management

Follow the hardware lifecycle from catalog approval through custody, CMDB linkage, and return.

Manage product, package, bundle, entitlement, installation, and usage evidence.

Validate vendor scope, review a purchase, and reconcile provider receipts.

Verify assigned counts, reconcile differences, and check replenishment and lease evidence.

Verify whether the original submission succeeded and record the provider reference without sending a duplicate order.

Move custody through the transfer actions and verify both stockrooms and the asset lifecycle.

Follow supplier onboarding, risk decisions, contract activation and the governed exit checks.

15 declared fields for Stockroom. Required fields include Stockroom name, Code, Organization, Site / location.

14 declared fields for Hardware model. Required fields include Model name, Manufacturer, CI / asset class, Planned lifecycle (years).

11 declared fields for Hardware catalog item. Required fields include Catalog item name, Fulfillment type, Asset class, Available models.

28 declared fields for Hardware asset request. Required fields include Request type, Catalog item, Requested model, Quantity.

10 declared fields for ERP integration. Required fields include Integration name, ERP provider, Secret Manager credential alias, Provider configuration.

24 declared fields for Asset purchase order. Required fields include Asset request, Hardware model, Quantity, Receiving stockroom.

45 declared fields for CMDB hardware asset. Required fields include Asset tag, Serial number, Asset name, Asset class.

37 declared fields for Hardware CI lifecycle workflow. Required fields include Lifecycle flow, Workflow state, Requested by, Effective date.

16 declared fields for Stockroom transfer. Required fields include Source stockroom, Destination stockroom, Assets, Transfer state.

15 declared fields for CMDB software product. Required fields include Product name, Publisher, Product type, License metric.

16 declared fields for Installation catalog item. Required fields include Package name, Software product, Package type, Package version.

9 declared fields for Deployment integration. Required fields include Integration name, Provider, Credential secret alias, Provider configuration.

26 declared fields for Software entitlement. Required fields include Entitlement number, Software product, License metric, Quantity owned.

20 declared fields for Software contract. Required fields include Contract name, Contract number, Vendor, Contract owner.

15 declared fields for Software usage record. Required fields include Software product, Usage source, Usage status.

17 declared fields for Software installation CI. Required fields include Software product, Installed on hardware / device CI, Discovery source, Installation status.

21 declared fields for License allocation. Required fields include Entitlement, Software product, Allocated to, Quantity.

15 declared fields for Asset cost event. Required fields include Asset domain, Cost event, Amount, Currency.

14 declared fields for Software bundle. Required fields include Bundle name, Bundle type, Version, Platform.

10 declared fields for Bundle package. Required fields include Software bundle, Installation package, Install order.

19 declared fields for Bundle deployment. Required fields include Software bundle, Target device / CI, Deployment state.

20 declared fields for Vendor account. Required fields include Name, Vendor code.

Connect an approved deployment adapter implementing the Qintorava bundle/target/package API contract. The adapter is responsible for native provider execution and must return a real execution ID and status.

Connect an approved deployment adapter implementing the Qintorava bundle/target/package API contract. The adapter is responsible for native provider execution and must return a real execution ID and status.

Connect an approved deployment adapter implementing the Qintorava bundle/target/package API contract. The adapter is responsible for native provider execution and must return a real execution ID and status.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.

Provider REST API integration with an explicit request/response mapping. A provider-specific API schema or approved adapter is required; selecting a product does not configure its API.