> For the complete documentation index, see [llms.txt](https://developers.awake.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.awake.ai/port-vision/description-of-port-vision.md). # Description of Port Vision ### Why Port Vision? For making available web & cloud based modern, delightful to use and AI analytics powered tool for port call planning and optimization. Main target groups and small to medium ports that do not have modern tools for planning efficient, safe port call turnarounds. Bringing together key user groups in the port to share relevant data, coordinate for optimized operations and when disruptions happen come back to planned state as fast as possible. ### Who are target users? * Small to medium size maritime port of all kinds * Port authorities and traffic managers * Port terminals and traffic & resource planners * Shipping agents representing vessels * Pilots helping vessels on safe arrivals and departures * Towing companies to assisst vessels * Port service providers of all kinds * Medium to large ship yards --- # 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://developers.awake.ai/port-vision/description-of-port-vision.md?ask=&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.