> For the complete documentation index, see [llms.txt](https://ynteq.gitbook.io/ynteq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ynteq.gitbook.io/ynteq-docs/ynteq-features/features-overview.md).
# Features overview
Welcome to the platform
Welcome to the Ynteq CMMS – The software that helps you to streamline and optimize your maintenance operations.
In this guide, we would like to introduce you to our platform and explain how to work with some of the core features. Also, we’ll give you some suggestions on how to optimally integrate our platform with your operations – even if you have unique processes that are relevant in your production facility.
Let’s get to it!
Let’s talk about the menu first, and see what you can do at each tab:
Analysis – Here you can deep-dive on operational issues, asset health or team expertise
Work orders – The core of the system: where you & your team manage day-to-day activities
Work requests – All users can access this page to request works to the maintenance team
Periodic Maintenance – The place where you build & maintain your maintenance regime
Assets – A ledger of all assets and the important information for physical asset at your site
Parts Inventory – Keep track of spare parts and investigate inventory levels
Vendors – Manage your vendors and their contact details
So, now we know what to do where, let’s start with the heart of the system, the most important functionality: Work Orders!
---
# 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://ynteq.gitbook.io/ynteq-docs/ynteq-features/features-overview.md?ask=&goal=
```
`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.