> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/project-overview/introduction.md).
# Introduction
### Overview
**OCS Inventory NG (Open Computer and Software Inventory Next Generation)** is a free and open-source software solution designed to automate the inventory of IT assets. It collects detailed information about the hardware and software on networked machines running the [**OCS Inventory Agent**](/administrator-docs/agent-setup/agent-overview.md).
Users can access and manage the inventory through the web interface, which also supports **package deployment** based on customizable search criteria. The **IpDiscover** and **SNMP** scanning features help enrich the inventory by providing insights into networked assets and connected devices.
### **The OCS Workflow**
Agents installed on devices collect inventory data and send it to the OCS server. The server processes and stores the data in its database, making it available through the web console. Communication is two-way: while agents report their inventory, administrators can also deploy configurations or packages back to devices from the console.
OCS workflow
### What's New in OCS Inventory 3.0?
The 3.0 version aims to maintain similar functionality while introducing significant improvements in scalability, performance, adaptability, and user experience. We also updated the application to align with modern standards and adopted accessible technologies to ensure its relevance and ease of use.
Want more details? Head to [v2 vs v3: What’s changed?](/project-overview/v2-vs-v3-whats-changed.md)
Coming from OCS Inventory 2.X? Check out our [Migration guidelines](/project-overview/migration-guide.md)!
---
# 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://documentation.ocsinventory-ng.org/project-overview/introduction.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.
