Model Settings
Step 1 — Configure your project identity and measurement units
The Model Settings screen is the first step when creating a new simulation. It establishes the project identity (who this simulation is for) and the measurement units that will be used throughout every subsequent input screen and report. Think of it as setting the foundation before you begin entering nutritional data.
Project Information
These fields help you organise your simulations and identify them later, especially when you accumulate multiple saved sessions. They also populate the printable overview page, which you can share with clients.
| Field | Description |
|---|---|
| Session Name | An optional label for this simulation project. Use something descriptive such as "Farm de Vries — Summer 2026" or "Trial Run — Low CP Diet". This name appears in the session list when you load saved simulations, so a clear name saves time later. |
| Customer Name | The name of the client or farm this simulation is prepared for. This is optional and purely informational — it appears on the overview and print pages so you can hand a professional-looking report to your client. |
| Customer Address | The client's location or farm address. Like Customer Name, this field is optional and appears only on the printable overview page. You can enter multiple lines if needed. |
Unit Configuration
The unit settings determine how values are entered and displayed across the entire model. Choose the units that match the conventions you and your client are most comfortable with. All three unit fields — energy, nutrient, and temperature — affect every input screen and every report.
Energy Unit
Controls how energy values are expressed throughout the model, both when you enter feed energy concentrations and when you read results such as energy intake or requirements.
| Option | Description |
|---|---|
| MJ | Megajoules — the standard scientific unit for energy in animal nutrition. Widely used in academic literature and international feed tables. |
| Kcal | Kilocalories — a common energy unit in several regions, particularly in North and South America. If your feed supplier provides energy values in Kcal, selecting this option avoids manual conversion. |
| EW | The Dutch energy evaluation system (EW, "Energie Waarde") used by Schothorst Feed Research. One EW equals 8.8 MJ of net energy. This is the standard unit in the Netherlands and is common among SFR clients. If you work with Dutch feed tables or SFR feed formulations, this is likely the most convenient choice. |
Your choice here directly affects how you will enter feed energy values on the Diet & Feeding screen. For example, a feed with a net energy of 9.68 MJ would be entered as 9.68 in MJ mode, as 2313 in Kcal mode, or as 1.10 in EW mode. Results in reports and charts will also reflect the chosen unit.
Nutrient Unit
Determines how nutrient concentrations (such as digestible lysine, methionine, threonine, and other amino acids) are expressed in feed compositions and reports.
| Option | Description |
|---|---|
| g/kg | Grams per kilogram of feed. This is the default and is widely used in European feed formulation. A lysine content of 8.5 g/kg means there are 8.5 grams of digestible lysine in every kilogram of feed. |
| % | Percentage of feed. Common in some regions and feed databases. A lysine content of 0.85% is equivalent to 8.5 g/kg. The conversion is straightforward: 1% = 10 g/kg. |
Temperature Unit
Choose between Celsius and Fahrenheit for temperature inputs. This affects the Health & Climate input screen, where you enter barn temperature data that the model uses to estimate thermal stress effects on feed intake and growth.
Units affect all input screens
The units you choose here affect all subsequent input screens. If you change units after entering feed compositions, the values will be automatically converted. You do not need to re-enter any data — the model handles the conversion for you. However, it is good practice to set your preferred units before you start entering detailed feed and nutrient data, so the numbers you see always match the conventions you are used to.
Scenario Comparison
Alternative Scenario
The Alternative Scenario toggle enables side-by-side comparison of two different sets of inputs, called Scenario A and Scenario B. When you turn this on, most input pages will display two columns, allowing you to define different parameters for each scenario. The output reports will then show results for both scenarios together, making differences easy to spot.
This feature is especially useful when you want to compare:
- Different diets — for example, a standard feed versus a lower-protein formulation, to see how amino acid balance affects growth and feed conversion.
- Different genetics — comparing growth curves and feed efficiency between two genetic lines or sire lines.
- Health scenarios — modelling a healthy barn versus a barn with a chronic health challenge to quantify the economic impact.
- Climate conditions — comparing summer versus winter performance by varying temperature inputs.
- Economic scenarios — testing the effect of different feed prices or pig prices on profitability.
When the toggle is enabled, the Scenario A and Scenario B name fields become editable. Give each scenario a descriptive name (for example, "Standard Diet" and "Low CP + AA") so you can easily identify them in the reports.
Duplicating a Session
Save as Duplicate
The Save as Duplicate button creates an exact copy of the current session, including all inputs you have entered so far. The duplicate is saved as a separate session with its own name (the original name with "Copy" appended).
This is useful when you want to create a variation of an existing simulation without losing the original. For example, you might duplicate a completed simulation and then change only the feed strategy or the genetics to see how that single change affects the outcome. Since all other inputs remain identical, any difference in results can be attributed directly to the change you made.
Save before duplicating
Make sure you have saved your current session before using Save as Duplicate. Any unsaved changes in the current session will be included in the duplicate, but the original session will still reflect its last saved state.