> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/getting-started/platform-overview/parameters.md).
# Parameters
Establish a live data backbone for your engineering workflows. Stop chasing down key values in siloed tools and give your team a single, authoritative source for the data that drives your design.
Start using parameter sets to keep track of the data you care about or pair them with [Scripts](/features/scripts.md) to get *oh so fresh* analyses at your fingertips.
Explore [Connect your data](/integrations/connect-your-data.md) to see what types of data you can connect.
### Create a Single Source-of-Truth for Critical Design Data
{% columns %}
{% column %}
Connect Parameters to live data from your most important engineering tools, eliminating manual data entry and stale information.
**Link directly to values from integrated sources like:** \
**- Component mass from CAD like**[Solidworks PDM](/apps/s/solidworks-pdm.md) and [Onshape](/apps/o/onshape.md) \
**- Simulation results from** [Scripts](/features/scripts.md) **in** [MATLAB](/apps/m/matlab.md)**,** [Python](/apps/p/python.md)\
**- Part data from PLM/PDM systems like** [Teamcenter](/apps/t/teamcenter.md)**,** [Duro](/apps/d/duro.md) \
**- and more.**
{% endcolumn %}
{% column %}
* Help your team view product data without overpaying for access to expensive engineering tools
* Define values manually for static inputs, then seamlessly update them to a live link as your design matures
* Organize your parameters into parameter sets and folders intuitively.
{% endcolumn %}
{% endcolumns %}
### Build an Authoritative and Interconnected Data Model
{% columns %}
{% column width="50%" %}
Use Parameters to represent key performance indicators (KPIs), technical budgets (mass, power, cost), and other critical system values that are **authoritative** and **interconnected**.
{% endcolumn %}
{% column width="50%" %}
* Create a web of data where a change in one source (like a CAD file) automatically propagates to all dependent parameters and analyses, preventing design decisions from being made on outdated numbers.
* Easily view live updates by subscribing to parameter sets and getting notifications when your watched items change
{% endcolumn %}
{% endcolumns %}
### Power Live Scripts and Automate Analysis
{% columns %}
{% column %}
Use Parameters as direct inputs for live scripts that run automatically when underlying data changes.
**Trigger complex calculations, trade studies, and analyses without manual intervention.**
{% endcolumn %}
{% column %}
* Create the parameters you'll use for your analysis. Fill in values manually or link them directly to any Violet entity's data.
* Open [Scripts](/features/scripts.md) and create variables that are linked to parameters (inputs or outputs).
* Write your analysis code in Matlab, Python, or Julia.
* Set the script to "live" and get automatic updates when the results are updated.
{% endcolumn %}
{% endcolumns %}
### Power your VCRM with Parameters and Requirements
{% columns %}
{% column %}
Parameters can link directly to math-aware [Requirements](/features/requirements.md) allowing a dynamic look at your compliance as well as a link to your verification artifacts.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### Explore Parameters-Related Features
---
# 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.violetlabs.com/getting-started/platform-overview/parameters.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.