# Ollama Modelfile Generator for an ERP Assistant

> Source: https://netray.co/tools/ollama-modelfile-generator-for-erp-assistant
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Build a Modelfile that bakes a grounded, read-only ERP system prompt and sane parameters into a local Ollama model.

## Category

developer

## Audience

- IT manager
- ERP analyst
- Developer

## Tool

**Kind:** template

**Output:** code

**Language:** text

**Fields:**

#### Base model tag

**Key:** base

**Type:** text

**Default:** qwen3:14b

#### New model name

**Key:** name

**Type:** text

**Default:** erp-assistant

#### ERP system

**Key:** erp

**Type:** text

**Default:** Infor SyteLine

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Context window (num_ctx)

**Key:** ctx

**Type:** number

**Default:** 8192

#### Temperature

**Key:** temp

**Type:** text

**Default:** 0.1

#### Top p

**Key:** top_p

**Type:** text

**Default:** 0.9

#### Extra house rules

**Key:** rules

**Type:** textarea

**Default:** Quote the table or report name you used. Never guess a part number or a price. Say 'not found in the data provided' when the context lacks the answer.

**Blocks:**

#### Modelfile

**Body:** FROM {{base}}

PARAMETER num_ctx {{ctx}}
PARAMETER temperature {{temp}}
PARAMETER top_p {{top_p}}
PARAMETER repeat_penalty 1.05

SYSTEM """
You are the internal assistant for {{company}}, answering questions about data from {{erp}}.
You only use the context supplied in the conversation. You are read-only: never offer to change, create or delete ERP records.
If asked to perform a write action, explain that a person must do it in {{erp}}.
{{rules}}
"""

#### Create and run

**Body:** ollama create {{name}} -f Modelfile
ollama run {{name}}

#### Call it from a script or integration

**Body:** curl http://localhost:11434/api/chat -d '{
  "model": "{{name}}",
  "stream": false,
  "messages": [
    {"role": "user", "content": "Summarise open purchase orders past due."}
  ]
}'

**Notes:** Verify parameter names against your Ollama version. A bigger num_ctx uses more memory; raise it only as far as your prompts need. A system prompt is guidance, not a security control: enforce read-only access in the database or API role, not in the prompt.

## Content

**Intro:** Ollama lets a team stand up a local model in minutes, which makes it a good pilot tool for ERP questions. A Modelfile captures the base model, parameters and house rules so everyone gets the same behavior.

**Sections:**

#### How to use it

**Body:** Choose a base model you already pulled with ollama pull, give the assistant a name, and describe your ERP and company. Paste the generated Modelfile into a file called Modelfile, run the create command and then chat. The third block shows the REST call that integrations use, so your scripts can query the same model on port 11434.

#### Why these parameter choices

**Body:** A low temperature keeps answers about numbers and statuses consistent from run to run. The context window must be large enough to hold the retrieved ERP rows or document excerpts you paste in, but Ollama defaults can be small, so setting num_ctx explicitly avoids silent truncation. A mild repeat penalty reduces looping on tabular output.

**Bullets:**

- temperature near 0.1 for factual lookups
- num_ctx sized to your retrieved context
- SYSTEM text sets scope and refusal behavior
- One Modelfile per use case keeps prompts clean

#### Common mistakes

**Body:** The biggest error is treating the system prompt as a security boundary. A model can be talked out of its instructions, so permissions belong in the database role or API scope. Another is leaving the default context size and wondering why long reports are cut off. Finally, pilots that stay on a laptop model should be sized properly before many users depend on them.

**Cta:** Netray can take a working Ollama pilot to a governed, read-only ERP assistant on your own servers, including retrieval and audit logging.

**Faq:**

#### Does the Modelfile give the model access to my ERP?

**Answer:** No. It only configures the model. Access to ERP data comes from whatever retrieval or tool layer you connect, which should use a read-only account with the same permissions as the asking user.

#### What context size should I set?

**Answer:** Set it to cover your system prompt, the retrieved rows or passages and the answer. Many pilots use 8192 to 16384. Larger windows consume more memory and slow responses.

#### Can I run Ollama without internet?

**Answer:** Yes after the model files are present. Pull models on a connected machine and move them across using your approved process, or copy the Ollama models directory to the isolated host.

#### When should I move from Ollama to vLLM?

**Answer:** When several users hit the endpoint at once or you need higher throughput on server GPUs. Ollama is excellent for pilots and single-user tools.

## Search terms

ollama modelfile example, ollama modelfile system prompt, ollama num_ctx setting, ollama create model from modelfile, ollama api chat curl, local llm for erp pilot, ollama temperature low for data answers

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json