> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-5.28/fleet-allocation-and-scheduling/getting-started.md).

# Getting Started

In Fleet Allocation and Scheduling (FAS) you can work on voyages in the planning phase and allocate them to vessels. Available voyages and vessels are:

#### Voyages with status

* Scheduled (Unallocated)
* Scheduled (Allocated)
* Nominated

#### Vessels with the following properties

* "Schedulable" in the vessel master data
* FleetExitDate empty or in the future

{% hint style="info" %}
Vessels which don't have any voyage in their schedule are not displayed in the open positions board or schedule view. However, they are available to allocate and move to in the voyage drawer, and to create scenarios with them.
{% endhint %}

**Master and Scenario**

We distinguish between the master schedule and scenarios.

The master schedule shows the current plan for the fleet and commitments. It is directly linked to the rest of the VMS. 

Scenarios help the scheduler to evaluate different options when scheduling. Scenarios are independet from other VMS modules. In the scenario list you find all scenarios, edit them and create new ones. You use the scenario details view to allocate and unallocate voyages in a scenario.

#### Views

For master and scenarios we have two different views available: the open positions board and the gantt board (schedule view).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dataloy.com/release-5.28/fleet-allocation-and-scheduling/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.