english

Configure Your Product Package i

Use this form to tailor your product package to suit your specific needs.

  • Review each feature and select whether it should be included. For features available in multiple units, specify the desired quantity.
  • The table outlines what is included by default in each package tier (Budget, Basic, Standard, Pro, Premium).
  • Choose a base configuration by clicking on a tier heading.
  • Any selected features or quantities beyond the included levels will be priced according to the listed add-on rates.

💡 The system will automatically calculate the optimal package and any necessary add-ons to ensure the lowest possible total cost based on your selections.

If you have any questions or would like guidance, feel free to reach out—we’re here to help.

📞 Phone: +46 (0)76-0254007
✉️ E-mail: info@simulationpartner.se

Make your
custom
selection here
Reset Budget Basic Standard Pro Premium
Package price 19 000 kr 34 000 kr 59 000 kr 109 000 kr 199 000 kr
Current add-on price 200 000 kr 140 000 kr 70 000 kr 60 000 kr 40 000 kr
Total price 219 000 kr 174 000 kr 129 000 kr 169 000 kr 239 000 kr
Type of system Budget Basic Standard Pro Premium
Production line (simple flow)

A Production line can represent various types of manufacturing lines.

Examples of Production lines include:

  • Machining line
  • Assembly line
  • Casting line
  • Welding line
  • Painting line

Capabilities and limitations in a Simple Flow:

  • Parallel stations are supported.
  • Complex branching is not supported (see Complex Flow).
  • Variant-specific flows are not supported (see Complex Flow).
19000
Production line (complex flow)

The following are included in Production line (Complex Flow):

  • All features from Production line (Simple Flow)
  • Combined flows:
    • Two or more flows merging into one
    • One flow splitting into two or more flows
  • Different flows for different variants
34000
Assembly line (incl. Internal logistics)

Included in Assembly line (incl. Internal logistics):

  • All features from Production line (Simple Flow)
  • BOM (Bill of Materials) list for each assembly station
  • Transport solutions for assembly parts from storage to the assembly line:
    • Forklift (transports pallets)
    • AGVs (transports boxes)
  • Storage for incoming goods
59000
Complex assembly line (incl. Internal logistics) 109000
Warehouse 109000
General objectives Budget Basic Standard Pro Premium Add-on cost / unit Add-on cost
Graphics 3D model

All our simulation models are built in 3D to ensure realistic visualization, which boosts both credibility and acceptance.

0
Graphics Custom color of variants

All variants are assigned randomly generated colors to help distinguish them visually.

To apply custom colors, this feature must be included in the order.

5000
Graphics Custom color of objects

All static objects (e.g., stations, buffers) use a standard color by default.

To apply custom colors, this feature must be included in the order.

10000
Graphics Custom graphic of objects

All static objects (e.g., stations, buffers) are displayed with a standard 3D graphic by default.

To appply custom graphic, this feature must be included in the order and the corresponding graphic files must be attached.

0 0 0 0 0 1000
Graphics Custom animation of objects

By default, all objects (except workers) are represented using static 3D graphics.

If animated graphics are required (e.g., a tool moving toward a part during processing), this feature must be included in the order.

Note! The animation of objects do NOT affect the simulation results.

0 0 0 0 0 5000
Experiments/Optimizations Budget Basic Standard Pro Premium Add-on cost / unit
Number of line configurations

The static objects included in the model, along with their connections, form a Line Configuration.

Typically, only one Line Configuration is needed. However, multiple configurations may be required—for example, when purchasing a new line and different machine or line suppliers propose alternative solutions.

Another case where multiple Line Configurations are needed is when simulations of several different flows are included in the same order.

1 2 4 8 16 10000
Number of output values

Output values are various result data points, often determined by the simulation result.

Examples of Output values include:

  • Throughput per hour (in the line)
  • Lead time (in the line)
  • Work in process (in the line)
3 6 8 16 32 5000
Number of experiment parameters

Experiment parameters are input data points whose values vary between different experiments.

Examples of experiment parameters include:

     
  • Cycle time in Station 1
  •  
  • Capacity (number of places) in Buffer 1
  •  
  • Set-up time in Station 2
  •  
  • Batch size
1 4 8 16 32 5000
Number of experiments

Experiments represent different scenarios to be tested.

Examples:

  • “What happens if availability increases by 5%?” — this is one experiment.
  • “Which of the following three sequences gives the highest throughput per hour?” — this involves three experiments.
  • “Which batch size (between 1 and 101, in steps of 5) gives the highest throughput per hour?” — this results in 21 experiments (1, 6, 11, …, 101).

Another example, suppose you want to test the following:

  • 2 line configurations
  • 3 experiment parameters (for each configuration)
  • 4 values per parameter

This results in a total of: 2 × 3 × 4 = 24 experiments.

1 10 100 1000 5000 100
Max number of objects Budget Basic Standard Pro Premium Add-on cost / unit
Station objects

A Station object is a location where a part is processed and value is added to it.

Examples of Station objects include: Station, Parallel Station, Assembly Station, and Dismantle Station.

7 14 25 50 100 500
Buffer objects

A Buffer object is a location where a part can wait before continuing in the process flow.

Examples of Buffer objects include: Buffer and Store.

7 14 25 50 100 500
Variants

A Variant is a part type that differs from others in one or more defined ways, such as features, materials, dimensions, or configurations.

In flow simulation, it is only relevant to distinguish between Variants if they impact the flow in some way. This could include differences in cycle time, changeover time, scrap rate, or the specific path a variant follows through the production process.

1 5 20 50 100 500
Shift calendars

A Shift calendar is used to define when different equipment and resources are operational.

  • Configure shift times during the week (e.g., day, evening, or night shifts).
  • Set up operational calendars across the year (e.g., holidays, maintenance periods, seasonal schedules).
0 1 3 10 20 1000
Input data type Budget Basic Standard Pro Premium Add-on cost
Cycle time

Cycle time is the minimum time required to process a part in a station object, including loading and unloading, but excluding any waiting time.

Cycle time (constant time)

Constant time refers to a fixed duration that repeats in every cycle.

0
Cycle time Detailed cycle time (custom distribution)

Detailed cycle time (custom distribution) refers to a cycle time that varies for each cycle based on a specified statistical distribution.

Examples of supported distributions include:

  • Uniform
  • Normal
  • Lognormal
  • Negative Exponential
  • Weibull
  • Triangular
5000
Cycle time Cycle time (per variant)

Detailed cycle time (per variant) allows you to define a specific cycle time for each variant used in the simulation model.

This enables more accurate modeling when different variants require different processing times.

10000
Stop data

Stop data refers to the values that describe how frequently and how long an object is in a failed state.

Stop data (AVB/MTTR)

With Stop data (AVB/MTTR), failures are described using two metrics:

  • Availability (AVB): The percentage of time an object is not in a failed state.
  • MTTR (Mean Time to Repair): The average time it takes to repair an object after a failure.

Note:

  • In simulation models, the relevant MTTR value typically reflects the entire stop duration, often referred to as MDT (Mean Down Time). This includes all phases of a stop, such as:
    • Waiting for an operator
    • Waiting for maintenance
    • Waiting for spare parts
    • Restarting the station
    • Verifying the quality of produced parts
  • An exception applies when repair resources (e.g., maintenance personnel) are modeled to simulate waiting times. In this case, the MWT (Mean Waiting Time) should be subtracted from MDT to obtain the correct MTTR.
  • If needed for analysis, other parts of the stop duration can also be excluded, but this requires custom logic.
0
Stop data Detailed stop data (several stop groups)

In some scenarios, Stop data follows two or more statistical distributions rather than just one.

This typically occurs when there are multiple sources of stops, such as:

  • Breakdowns: Failures where something is physically broken and requires replacement or special handling (often involving specialized personnel).
  • Small stops: Minor interruptions where the object can usually be restarted without major intervention.

The presence of multiple error types can often be identified by observing that the input data aligns with more than one distribution pattern.

10000
Stop data Detailed stop data (custom distribution)

Stop data can be defined in two ways:

  1. Using Availability and MTTR, see (AVB/MTTR)

    Note: With this approach, the interval and duration are calculated from the Availability and MTTR values. The simulation uses a Lognormal distribution for the interval and a Weibull distribution for the duration.

  2. Using interval and duration directly:
    • Interval: Mean time between stops
    • Duration: Mean time for each stop

    This method allows you to specify a custom distribution for both the interval and the duration.

    Examples of supported distributions include:

    • Uniform
    • Normal
    • Lognormal
    • Negative Exponential
    • Weibull
    • Triangular

The feature Detailed stop data (custom distribution) enables the second approach.

10000
Set-up

A station that requires Set-up needs preparation time before it can begin processing. This typically includes activities such as changeovers between variants or tool changes.

In the simulation model, Set-up can be defined according to two main principles:

  1. Set-up due to change of variant: Triggered when the incoming part differs from the previous one.
  2. Set-up after a certain number of processed parts: Triggered periodically, based on quantity thresholds.
10000
Set-up Detailed set-up time (custom distribution)

Detailed set-up time (custom distribution) allows the set-up duration to vary randomly according to a specified statistical distribution.

This makes it possible to more accurately represent the variability in set-up times within the simulation model.

10000
Set-up Set-up time (per variant)

Set-up time (per variant) allows you to define different set-up durations between specific variant transitions using a variant-to-variant matrix.

For example, the Set-up time can be specified individually for transitions such as:

  • A → B
  • A → C
  • B → A
  • B → C
  • C → A
  • C → B

This enables more accurate modeling of changeover times between different product variants.

10000
Set-up Set-up settings

Set-up settings allow you to define more precisely when a set-up should occur.

Available options include:

  • Only perform set-up when the station is empty — ensures that set-up is triggered only when no parts are present at the station.
  • Perform set-up “Before Next Part” or “After Last Part” — applicable only for Set-up after a certain number of processed parts:, not for Set-up due to change of variant.
10000
Scrap Scrap value

The Scrap rate is a percentage that defines how much of the processing at a station results in parts being scrapped.

A part marked as scrap may either continue through the process flow to the end or be removed from the flow at a designated point.

In analysis, scrap is treated as a quality loss.

10000
Scrap Scrap settings

Scrap settings allow you to define the specific positions in the process flow where parts marked as Scrap should be removed from the flow.

10000
Workers

Workers in the simulation model make it possible to simulate the impact of different numbers of available workers on the process.

When using workers in the model, it is important to exclude any pre-existing worker-related waiting times from the input data. Instead, let the simulation dynamically generate waiting times based on actual worker availability during runtime.

Operator, Set-up staff, Maintenance

There are three default worker types in the simulation model: Operator, Set-up Staff, and Maintenance.

  • Operator: Performs the actual processing at a station, such as assembly tasks.
  • Set-up Staff: Handles set-up activities, indicating that these tasks require separate personnel.
  • Maintenance: Responsible for repairing objects when they fail.
10000
Workers Electric/Mechanical maintenance

Adding Electrical and Mechanical maintenance categories allows you to split maintenance tasks into two distinct types. This enables a more precise analysis of how waiting times impact the overall process flow.

10000
Workers Custom worker

When Shift calendars are included, you can always choose from 12 predefined Shift Times (1–6 shifts, each available with or without breaks).

To apply customized shift times, this feature must be included in the order.

10000
Shift calendars Customized shift times

Note: It is quite common to exclude Calendars in a Flow Simulation model.

However, if a Calendar is required, both a Swedish and an American Calendar for the current year are automatically included when Shift calendars are enabled.

To use a Customized calendar, this feature must be included in the order.

5000
Shift calendars Customized calendars 5000
Analysis Budget Basic Standard Pro Premium Add-on cost
BottleneckAnalysis

The BottleneckAnalysis is the primary tool for analyzing flow effectiveness and identifying losses in the system.

Functions of the BottleneckAnalysis includes:

  • Calculates the mean cycle time for each station during the simulation run and can therefor present statistics as parts/hour in charts.
  • Allows grouping of two or more station objects into a single operation step for combined analysis.
  • Identifies the bottleneck operation in the system and enables it to be highlighted.
  • Displays loss charts from three time perspectives:
    • OEE – based on Planned Production Time
    • OOE – based on Total Operations Time
    • TEEP – based on All Time
  • Supports input of an ideal cycle time to distinguish speed loss from working time, and are therefor able to recalculating statistics accordingly.
  • Enables identification of quality loss due to scrapped parts.
  • Allows separation of waiting time into:
    • Waiting for parts
    • Waiting for resources
    This helps identify line constraint losses in the analysis.
Level 1-2

Level 2 is the standard analysis level in Flow Simulation software. At this level, the different states of station objects form the basis of the statistical output.

States in Level 2 include:

  • Working
  • Setting-up
  • Waiting
  • Blocked
  • PoweringUpDown (start-up and shut-down time)
  • Stopped
  • Failed
  • Paused (unplanned production time)
  • Unplanned (non-operating time)

The BottleneckAnalysis feature enhances Level 2 by adding the following states:

  • Working (Possible bottleneck)
  • Waiting for resources
  • Quality loss
  • Speed loss

Level 1 provides an aggregated view of losses using standardized categories:

  • Working (OEE / OOE / TEEP)
  • Quality losses
  • Performance losses
  • Line constraints
  • Availability losses
  • Planned losses (used only in OOE/TEEP calculations)
  • Non-operating losses (used only in TEEP calculations)
15000
BottleneckAnalysis Level 3

Level 3 provides an in-depth analysis by breaking down key loss categories into detailed subcategories.

Quality Losses:

  • Scrap
  • Processing scrap
  • Rework

Waiting for Resources:

  • Waiting for operator
  • Waiting for set-up staff
  • Waiting for maintenance

Setting Up:

  • Setting up for variant
  • Setting up after n parts
  • (Tool change)

Start-up / Shut-down Losses:

  • Start-up loss
  • Pause down loss
  • Shut-down loss

Stopped By (dynamic loss categories from user input):

  • Stopped by Failure (failure name)
  • Stopped by Failure (failed object + failure name)
  • Stopped by Object (StoppedBy object name)
  • Stopped by Object (other failed object name)

Failed (dynamic loss categories from customer input):

  • Failure group name

Planned Loss (dynamic loss categories from customer input):

  • Label of unplanned shift times in the ShiftCalendar object

Non-operating Losses:

  • Weekly non-operating loss
  • Label of non-operating shift times in the ShiftCalendar object (dynamic loss categories from customer input)
  • Yearly non-operating loss
  • Label of non-operating days in the ShiftCalendar object (dynamic loss categories from customer input)
15000
BottleneckAnalysis Choose setting Level 1-2

Choose setting Level 1–2 makes it possible to choose from a set of predefined configurations.

Available options for Level 1:

  • SP STD
  • APQ Pl N
  • APQ Pl (not recommended)
  • APQ (not recommended)

Available options for Level 2:

  • SP STD
  • PlantSim default
5000
BottleneckAnalysis Choose setting Level 3

Choose setting Level 3 makes it possible to choose from a few predefined configurations:

  • SP STD (affected)
  • SP STD (causing)
5000
BottleneckAnalysis Custom settings Level 1-2

Custom settings Level 1-2 enables the following configuration options:

For Level 2:

  • Activate or deactivate additional states:
    • Working (Possible bottleneck)
    • Quality losses
    • Speed losses
    • Waiting for resources
  • Rename losses
  • Sort losses
  • Assign colors to losses

For Level 1:

  • Re-categorize Level 2 losses into Level 1 categories
  • Sort losses
  • Assign colors to losses
10000
BottleneckAnalysis Custom settings Level 3

Custom settings Level 3 enables the following configuration options:

  • Re-categorize Level 3 losses into corresponding Level 2 categories
  • Rename losses
  • Deactivate dynamic losses for the following categories:
    • Failures
    • Yearly non-operating losses
    • Weekly non-operating losses
    • Planned stops
    • Stopped by
10000
Report Budget Basic Standard Pro Premium
Customize report 10000
Support Budget Basic Standard Pro Premium Add-on cost
Delivery Budget Basic Standard Pro Premium Add-on cost
Simulation report

A Simulation Report is included with all deliveries.

The report contains the following sections:

  • Title page with creation details
  • General information
  • Model overview
  • All input data
  • Results from the BottleneckAnalysis
  • Statistical summaries

See the example report for more details.

0
Experiment report

An Experiment Report is included with all deliveries.

Since most simulations use dynamic input data, the results do not represent exact values. Instead, they are presented as statistical estimates.

The accuracy of the results depends entirely on the quality of the input data.

Example result:
Based on the given input data, the true mean throughput per hour is estimated to be between 10.1 and 10.3, with a 95% confidence level.

To produce statistically valid results, multiple replications (or observations) must be run for each experiment.

The combined outcome of these replications is summarized in the Experiment Report.

10000
EXE file

The simulation model is delivered as an EXE file (executable file), meaning it can be run without requiring Plant Simulation software or a license.

Important: This file is not editable. Changes in the simulation model can only be done in the Plant Simulation File.

10000
Plant Simulation file

Note! the Plant Simulation File is not included in the standard delivery package.

This is because the model is built using our standard library, which is deeply integrated into the simulation model and represents significant intellectual property.

If you have access to the Plant Simulation software, have a valid license and want to have the Plant Simulaiton File, include this in the order.

Important: The price of this add-on depends on the amount of functionality included in the simulation model, as this reflects the value embedded through our standard library. The price will be calculated automatically from the included features.

With access to the editable file, you can, for example, duplicate the model and adapt it to simulate another production line using our standard library components.

Base

The following objects (and functions) from the standard library are always included in the Plant Simulation File:

  • Stations (included in onPlausibility controls)
  • Buffers (included in onPlausibility controls)
  • Variants (now called Parts, included in onPlausibility controls)
25000
Plant Simulation file BottleneckAnalysis Level 1-2

If BottleneckAnalysis are included, the following functionalities in the object from the standard library are included in the Plant Simulation File:

  • Operation functionality
  • Possible Bottleneck functionality
  • Speed losses
  • Quality losses
  • Split of Waiting Waiting for parts / Waiting for others, has no effect unless Resources are defined
10000
Plant Simulation file BottleneckAnalysis Level 3

Losses included in Level 3

If BottleneckAnalysis Level 3 are selected, the following functionalities in the object from the standard library are included in the Plant Simulation File:

  • Internal losses: (doesn’t need any extra objects)
    • Waiting for operator
    • Waiting for set-up staff
    • Waiting for maintenance
    • Waiting for …
    • Set-up for variant
    • Set-up after a number of parts
    • Start-up loss
    • Shut-down loss
    • Failure 1, 2, 3, etc. (dynamic)
  • Losses from other obejcts:
    • StoppedBy (dynamic)
    • P_ShiftCalendar, including:
      • Pauses (dynamic)
      • Weekly non-operating losses (dynamic)
      • Yearly non-operating losses (dynamic)
15000
Plant Simulation file Resources

If Workers are included, the following objects from the standard library are included in the Plant Simulation File:

  • Workplace_Op
  • Workplace_Se
  • Workplace_Ma
  • Workplace_El (optional)
  • Workplace_Me (optional)
  • Workplace_Cu (optional)
  • Operator_Male
  • Operator_Female
  • SettingUpStaff_Male
  • SettingUpStaff_Female
  • Repairer_Male
  • Repairer_Female
  • WorkerColors (custom color definitions?)
  • WorkerColorMapping (mapping of roles to colors?)
15000
Source code

Important! Even if the Plant Simulation File is included in the delivery, you will not have access to the source code of our standard library.

This means you can use the library for your own modeling purposes, but you cannot modify it or view its internal implementation.