> For the complete documentation index, see [llms.txt](https://selenium-4.gitbook.io/nexus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://selenium-4.gitbook.io/nexus-docs/documentation/collateral-asset-administration/overview.md).

# Overview

Domínio de serviço BIAN responsável por manter o estado dos ativos de colateral de um cliente, incluindo avaliações agendadas e ad-hoc, e a confirmação da correta execução das tarefas de manutenção agendadas.

## Serviços disponíveis

* [Create Collateral Asset Account](/nexus-docs/documentation/collateral-asset-administration/operations/main.md)

## Exemplo de uso

Um cliente regista um veículo como ativo de colateral; o domínio cria a conta do ativo e passa a acompanhar o seu estado, incluindo avaliações periódicas ao longo da vida do colateral.

## Definição do papel

O domínio de Collateral Asset Administration mantém o estado corrente dos ativos de colateral do cliente, garantindo que as avaliações agendadas e ad-hoc são realizadas e que as tarefas de manutenção associadas a cada ativo são concluídas corretamente.

## Características principais

* Criar contas de ativos de colateral
* Manter o estado atualizado de cada ativo de colateral
* Confirmar a correta execução de avaliações e tarefas de manutenção agendadas


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://selenium-4.gitbook.io/nexus-docs/documentation/collateral-asset-administration/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.