PRACTICAL FILE

ENGINEERING SYSTEM MODELLING

& SIMULATION LAB
ETME-452

Department of Mechanical and Automation Engineering

Maharaja Agrasen Institute of Technology

Submitted To:- Mr Satish kumar

Submitted by: Arunav Sharma

Enrollment no : 75214808220
SN0 EXPERIMENT DATE REMARKS
EXPERIMENT-1

Problem

Replications: 1 Time Units: Hours

Key Performance Indicators

System Average Number Out 197
 Replications: 1 Time Units: Hours

Entity

Time

VA Time Minimum Maximum

Average Half Width Value Value

Entity 1 0.07050150 (Insufficient) 0.03375015 0.1166

NVA Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.00 (Insufficient) 0.00 0.00

Wait Time
Minimum Maximum
Average Half Width Value Value

Entity 1 2.2197 (Insufficient) 0.00 3.6405

Transfer Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.00 (Insufficient) 0.00 0.00

Other Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.00 (Insufficient) 0.00 0.00

Total Time
Minimum Maximum
Average Half Width Value Value

Entity 1 2.2902 (Insufficient) 0.03961327 3.6758

Other

Number In
Value

Entity 1 246.00

Number Out
Value

Entity 1 197.00

WIP
Minimum Maximum
Average Half Width Value Value
 Time
Replications: 1 Units:
Hours

Queue

Time

Waiting Time
Minimum Maximum
Average Half Width Value Value

Female.Queue 1.1489 (Insufficient) 0.00 1.9038

Femaleq.Queue 1.1006 (Insufficient) 0.00 1.8842

male.Queue 1.1810 (Insufficient) 0.00 1.8788

maleq.Queue 1.1441 (Insufficient) 0.00 1.9663

Other

Number Waiting
Minimum Maximum
Average Half Width Value Value

Female.Queue 6.5575 (Insufficient) 0.00 14.0000

Femaleq.Queue 7.3777 (Insufficient) 0.00 16.0000

male.Queue (Insufficient) 0.00 20.0000

10.2249

maleq.Queue (Insufficient) 0.00 19.0000

10.9057

Resource

Usage

Instantaneous
Utilization Minimum Maximum
Average Half Width Value Value

Resource 1 0.9794 (Insufficient) 0.00 1.0000

 Number Busy
Minimum Maximum
Average Half Width Value Value

Resource 1 0.9794 (Insufficient) 0.00 1.0000

Number
Scheduled Minimum Maximum
Average Half Width Value Value

Resource 1 1.0000 (Insufficient) 1.0000 1.0000

Scheduled
Utilization
Value

Resource 1 0.9794

Total Number
Seized
Value
Resource 1 420.00
EXPERIMENT-2
Problem

Replications: 1 Time Units: Hours

Key Performance Indicators

System Average Number Out 24
 Replications: 1 Time Units: Hours

Entity

Time

VA Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.3472 (Insufficient) 0.00 0.4167

NVA Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.00 (Insufficient) 0.00 0.00

Wait Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.6845 (Insufficient) 0.00 1.8063

Transfer Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.00 (Insufficient) 0.00 0.00

Other Time
Minimum Maximum
Average Half Width Value Value

Entity 1 0.00 (Insufficient) 0.00 0.00

Total Time
Minimum Maximum
Average Half Width Value Value

Entity 1 1.0318 (Insufficient) 0.00 2.2230

Other

Number In
Value

Entity 1 24.0000
 Number Out

Value

Entity 1 24.0000

WIP
Minimum Maximum
Average Half Width Value Value
Entity 1 1.6508 (Insufficient) 0.00 6.0000

Time
Replications: 1 Units:
Hours

Queue

Time

Waiting Time
Minimum Maximum
Average Half Width Value Value

Doctor.Queue 0.5000 (Insufficient) 0.00 1.0833

nurse1.Queue 0.3538 (Insufficient) 0.00 0.8063

nurse2.Queue 0.2730 (Insufficient) 0.00 0.6091

Other

Number Waiting
Minimum Maximum
Average Half Width Value Value

Doctor.Queue 0.6667 (Insufficient) 0.00 4.0000

nurse1.Queue 0.2830 (Insufficient) 0.00 4.0000

nurse2.Queue 0.1456 (Insufficient) 0.00 3.0000

Resource
Usage

Instantaneous
Utilization Minimum Maximum
Average Half Width Value Value

Resource 1 0.5556 (Insufficient) 0.00 1.0000

Number Busy
Minimum Maximum
Average Half Width Value Value

Resource 1 0.5556 (Insufficient) 0.00 1.0000

Number Scheduled
Minimum Maximum
Average Half Width Value Value

Resource 1 1.0000 (Insufficient) 1.0000 1.0000

Scheduled Utilization

Value

Resource 1 0.5556

Total Number Seized

Value
Resource 1 40.0000
EXPERIMENT-3

AIM: Study modelling environment of Arena Software

ARENA WINDOW

Arena Software

Arena software enables you to bring the power of modeling and simulation to your
business. It is designed for analyzing the impact of changes involving significant and
complex redesigns associated with supply chain, manufacturing, processes, logistics,
distribution and warehousing, and service systems. Arena software provides the
maximum flexibility and breadth of application coverage to model any desired level of
detail and complexity.

While you may not realize it quite yet, you now have the power to transform your
business. Whenever you and others in your organization are wondering “what if…?,”
you can look into the future to find the answer.

With Arena, you can:

Model: Model your processes to define, document, and communicate.

Simulate: Simulate the future performance of your system to understand complex
relationships and identify opportunities for improvement.
Visualize: Visualize your operations with dynamic animation graphics.

Analyze: Analyze how your system will perform in its “as-is” configuration and under
a myriad of possible “to-be” alternatives so that you can confidently choose the best
way to run your business.

The Arena modeling environment

If Arena is not already running, start it from the Windows Start menu and navigate to
Programs > Rockwell Software > Arena. The Arena modeling environment will open
with a new model window, as shown below.

To model your process in Arena, you’ll work in three main regions of the application
window. The Project Bar hosts panels with the primary types of objects that you will
work with:

Basic Process, Advanced Process, and Advanced Transfer panels: Contain the
modeling shapes, called modules that you’ll use to define your process.

Reports panel: Contains the reports that are available for displaying results of
simulation runs.

Navigate panel: Allows you to display different views of your model, including
navigating through hierarchical submodels and displaying a model thumbnail view.

In the model window, there are two main regions. The flowchart view will contain all
of your model graphics, including the process flowchart, animation, and other drawing
elements. The lower, spreadsheet view displays model data, such as times, costs, and
other parameters.
Map your process in a flowchart

Build a flowchart: The word itself— flowchart—suggests two of the main concepts
behind modeling and simulation. We’ll be building a chart—also referred to as a
process map or a model— that describes a flow.

We’ll start the flowchart using a Create module, from the Basic Process panel. This is
the starting point for the flow of entities through the model.
1. Drag the Create module from the Basic Process panel into the model window.

Process the applications

Next in our flowchart is a Process module, from the Basic Process panel, representing
the Review Application step.

1. So that Arena will automatically connect the Process to the Create module, be
sure that the Create module is selected.
2. Drag a Process module from the Basic Process panel into the model window,
placing it to the right of the Create. Arena will automatically connect the two
modules.
Decide whether applications are complete
After the Process, we have a Decide module, from the Basic Process panel.
Drag a Decide module to the right of the Process module.

Dispose the applications to terminate the process

Next we’ll place the Dispose module, from the Basic Process panel, representing
accepted applications, connecting to the True (right) output from the Decide shape.
1. Select the Decide shape so that our first Dispose will be connected automatically.
2. Drag a Dispose module to the right of the Decide module. Arena will connect it to
the primary (True) exit point of the Decide module. (We won’t include a graphic
display since you’re now familiar with the drag-and-drop sequence.)

Module
In Arena, modules are the flowchart and data objects that define the process to be
simulated. All information required to simulate a process is stored in modules.
For now, we’re working with flowchart modules—those that are placed in the model
window to describe the process. In the Basic Process panel, these are the first eight
shapes:

Create: The start of process flow. Entities enter the simulation here.
Dispose: The end of process flow. Entities are removed from the simulation here.
Process: An activity, usually performed by one or more resources and requiring some
time to complete.
Decide: A branch in process flow. Only one branch is taken.
Batch: Collect a number of entities before they can continue processing.
Separate: Duplicate entities for concurrent or parallel processing, or separating a
previously established batch of entities.
Assign: Change the value of some parameter (during the simulation), such as the
entity’s type or a model variable.
Record: Collect a statistic, such as an entity count or cycle time.
EXPERIMENT-4

AIM: Study basic process panel of Arena Software

STUDY: Basic Process Panel includes the flowchart modules to model the
process in simulation environment.

Flowchart modules:

Flowchart modules are the set of objects that are placed in the model
window to describe the simulation process.

Flowchart modules includes

a. Create
b. Dispose
c. Process
d. Decide
e. Batch
f. Separate
g. Assign
h. Record

Create module

DESCRIPTION
This module is intended as the starting point for entities in a simulation
model. Entities are created using a schedule or based on a time
between arrivals. Entities then leave the module to begin processing
through the system. The entity type is specified in this module.

TYPICAL USES
• The start of a part’s production in a manufacturing line

• A document’s arrival (e.g., order, check, application) into a

business process

• A customer’s arrival at a service process (e.g., retail store,

restaurant, information desk)
 Number of entities created

Dispose module

DESCRIPTION
This module is intended as the ending point for entities in a simulation model.
Entity statistics may be recorded before the entity is disposed.

TYPICAL USES
• Parts leaving the modeled facility

• The termination of a business process

• Customers departing the store

Number of entities that have been disposed

Process module

DESCRIPTION
This module is intended as the main processing method in the simulation.
Options for seizing and releasing resource constraints are available.
Additionally, there is the option to use a “submodel” and specify
hierarchical user-defined logic. The process time is allo- cated to the entity
and may be considered to be value added, non-value added, transfer, wait,
or other. The associated cost will be added to the appropriate category.

TYPICAL USES
• Machining a part
 • Reviewing a document for completeness

• Fulfilling orders

• Serving a customer

Indicator of a submodel process

Number of entities currently in

process

Decide module
DESCRIPTION
This module allows for decision-making processes in the system. It
includes options to make decisions based on one or more conditions (e.g.,
if entity type is Gold Card) or based on one or more probabilities (e.g.,
75%, true; 25%, false). Conditions can be based on attribute values (e.g.,
Priority), variable values (e.g., Number Denied), the entity type, or an
expression (e.g., NQ(ProcessA.Queue)).

There are two exit points out of the Decide module when its specified
type is either 2-way by Chance or 2-way by Condition. There is one
exit point for “true” entities and one for “false” entities. When the N-
way by Chance or by Condition type is specified, multiple exit points
are shown for each condition or probability and a single “else” exit.
The number of entities that exit from each type (true/false) is displayed
for 2-way by Chance or by Condition modules only.

TYPICAL USES
• Dispatching a faulty part for rework

• Branching accepted vs. rejected checks

Sending priority customers to a dedicated process

 Number of entities that have taken the True branch

Number of entities that have taken the False branch

Batch module:

DESCRIPTION
This module is intended as the grouping mechanism within the
simulation model. Batches can be permanently or temporarily grouped.
Temporary batches must later be split using the Separate module.

Batches may be made with any specified number of entering entities or

may be matched together based on an attribute. Entities arriving at the
Batch module are placed in a queue until the required number of
entities has accumulated. Once accumulated, a new representative
entity is created.

TYPICAL USES
• Collect a number of parts before starting
processing

• Reassemble previously separated copies of

a form

• Bring together a patient and his record

before commencing an appointment

Number of entities waiting to be batched

Separate module

DESCRIPTION
This module can be used to either copy an incoming entity into multiple
entities or to split a previously batched entity. Rules for allocating costs and
times to the duplicate are also specified. Rules for attribute assignment to
member entities are specified as well.

When splitting existing batches, the temporary representative entity that

was formed is disposed and the original entities that formed the group are
recovered. The entities pro- ceed sequentially from the module in the
same order in which they originally were added to the batch.

When duplicating entities, the specified number of copies is made and

sent from the module. The original incoming entity also leaves the
module.

TYPICAL USES
•Send individual entities to represent boxes removed from a
container

• Send an order both to fulfillment and billing for parallel

processing Separate a previously batched set of documents

The original leaves on this branch

Duplicates leave on this branch

Assign module

DESCRIPTION
This module is used for assigning new values to variables, entity
attributes, entity types, entity pictures, or other system variables.
Multiple assignments can be made with a single Assign module.
TYPICAL USES
• Accumulate the number of subassemblies added to a part

• Change an entity’s type to represent the customer copy of a multi-

page form

• Establish a customer’s priority

Record module

DESCRIPTION
This module is used to collect statistics in the simulation model.
Various types of observa- tional statistics are available, including time
between exits through the module, entity statistics (time, costing, etc.),
general observations, and interval statistics (from some time stamp to
the current simulation time). A count type of statistic is available as
well. Tally and Counter sets can also be specified.

TYPICAL USES
• Collect the number of jobs completed each hour

• Count how many orders have been late being fulfilled

Record the time spent by priority customers in the main check-out line
EXPERIMENT-5

AIM: Study basic process panel - more of Arena Software

STUDY: Basic Process Panel - more includes the Data modules to model
the process in simulation environment with extra features.

Data modules are the set of objects in the spreadsheet view of the model
that define the characteristics of various process elements, such as
resources and queues. Data modules includes:

a. Entity
b. Queue
c. Resource
d. Variable
e. Schedule
f. Set

Entity module

DESCRIPTION
This data module defines the various entity types and their initial
picture values in a simulation. Initial costing information and holding
costs are also defined for the entity.

TYPICAL USES
• Items being produced or assembled (parts, pallets)

• Documents (forms, e-mails, faxes, reports)

• People moving through a process (customers,

callers)

Queue module

DESCRIPTION

This data module may be utilized to change the ranking rule for a
specified queue. The default ranking rule for all queues is First In, First
Out unless otherwise specified in this module. There is an additional field
that allows the queue to be defined as shared.

TYPICAL USES
• Stack of work waiting for a resource at a Process module

• Holding area for documents waiting to be collated at a

Batch module

Resource module

DESCRIPTION
This data module defines the resources in the simulation system,
including costing infor- mation and resource availability. Resources may
have a fixed capacity that does not vary over the simulation run or may
operate based on a schedule. Resource failures and states can also be
specified in this module.

TYPICAL USES
• Equipment (machinery, cash register, phone line)

• People (clerical, order processing, sales clerks,

operators)

Variable module

DESCRIPTION
This data module is used to define a variable’s dimension and initial
value(s). Variables can be referenced in other modules (e.g., the Decide
module), can be reassigned a new value with the Assign module, and
can be used in any expression.

There are three methods for manually editing the Initial Values of a Variable
module:

• Via the standard spreadsheet interface. In the module

spreadsheet, rightclick on the Initial Values cell and select the
Edit via spreadsheet menu item. The values for two-
dimensional arrays should be entered one column at a time.
Array elements not explicitly assigned are assumed to have the
last entered value.
 • Via the module dialog box. In the module spreadsheet, right-
click on any cell and select the Edit via dialog menu item. The
values for twodimensional arrays should be entered one column
at a time. Array elements not explicitly assigned are assumed to
have the last entered value.

Via the two-dimensional (2-D) spreadsheet interface. In the module

spreadsheet, click on the Initial Values cell.

TYPICAL USES
• Number of documents processed per hour

• Serial number to assign to parts for unique

identification • Space available in a facility

Schedule module

DESCRIPTION
This data module may be used in conjunction with the Resource module to
define an operating schedule for a resource or with the Create module to
define an arrival schedule. Additionally, a schedule may be used and
referenced to factor time delays based on the simulation time. Duration-
formatted schedules are defined within this module. Calendar- formatted
schedules are defined by selecting Edit > Calendar Schedules > Time
Patterns.

TYPICAL USES
• Work schedule for staff, including breaks

• Breakdown patterns for equipment

• Volume of customers arriving at a store

• Learning-curve factors for new workers

Set module

DESCRIPTION
This data module defines various types of sets, including resource, counter,
tally, entity type, and entity picture. Resource sets can be used in the
Process modules (and Seize, Release, Enter, and Leave of the Advanced
Process and Advanced Transfer panels).

Counter and Tally sets can be used in the Record module. Queue sets can
be used with the Seize, Hold, Access, Request, Leave, and Allocate
modules of the Advanced Process and Advanced Transfer panels.

TYPICAL USES
• Machines that can perform the same operations in a
manufacturing facility

• Supervisors, check-out clerks in a store

• Shipping clerks, receptionists in an office

• Set of pictures corresponding to a set of entity types

Calendar schedule information Time Pattern

DESCRIPTION
A Time Pattern defines a series of values that change over time. For
example, a worker might be on duty during a standard work shift from
Monday through Friday. The avail- ability of the worker could be
represented as a value of 1 when he’s on duty, 0 when he’s off duty. The
time pattern that defines this availability schedule would list the changes
from on duty to off duty over the week.

Time patterns are saved in an Arena model in the Schedule module with a
Type set to Calendar. Their data are edited via the Time Pattern window,
which is opened from the Edit > Calendar Schedules > Time Patterns
menu option.

TYPICAL USES
• Weekly work schedules (e.g., 1-shift, 5-day
weeks; 2shift, 4-day weeks)

• Daily work patterns (e.g., 8-hour day with

30-minute lunch break)

• Arrival patterns (e.g., weekly customer

arrivals, daily part orders)
Calendar Exceptions

DESCRIPTION
An Exception defines a value that is to be applied for a resource over
some fixed period of time. The exception value overrides the base value
defined for the resource. For example, if a machine’s capacity was
scheduled to be available (value of 1) during second shift according to its
base time pattern, you could add an exception to change it to unavailable
for second shift on a particular day (e.g., December 30, 2005).

Exception data are edited via the Exception and Composite windows,
which are opened from the Edit > Calendar Schedules > Exceptions and
Display Composite menu options.

TYPICAL USES
• Overtime

• Holidays

• Regularly scheduled meetings

Calendar States

DESCRIPTION
A Calendar State defines a name that can be used in place of a numeric
value when defin- ing time patterns and exceptions. This can be useful if a
particular value (e.g., the number of workers in a pool of labor) needs to be
entered in multiple places, but may need to be modified. By entering the
state name in the time patterns/exceptions, you can modify the value
associated with the state, which will apply the new value in all of those
places.

States are defined by opening the States editor dialog box from within
the time pattern and exceptions editors.

TYPICAL USES
• Labor pool sizes

• Standard efficiency values

• Base arrival rates

EXPERIMENT-6

AIM: Study Advanced process panel of Arena Software

STUDY: This study presents the modules included on the Advanced

Process panel, where additional functionality for modeling simulation
process is explained.

Flowchart modules
Flowchart modules are the set of objects that are placed in the model
window to describe the simulation process. It includes:

1. Delay
2. Dropoff
3. Hold
4. Match
5. Pickup
6. ReadWrite
7. Release
8. Remove
9. Seize
10. Search
11. Signal
12. Store
13. Unstore
14. Adjust Variable

Delay module

DESCRIPTION
The Delay module delays an entity by a specified amount of time.

When an entity arrives at a Delay module, the time delay expression is

evaluated and the entity remains in the module for the resulting time period.
The time is then allocated to the entity’s value-added, non-value added,
transfer, wait, or other time. Associated costs are calculated and allocated as
well.
 TYPICAL USES
• Processing a check at a bank

• Performing a setup on a machine

• Transferring a document to another department

Dropoff module

DESCRIPTION
The Dropoff module removes a specified number of entities from the
entity’s group and sends them to another module, as specified by a
graphical connection. Group user-defined attribute value and internal
attributes may be given to the dropped-off entities based on a specified
rule.

TYPICAL USES
• Loading shelves with product

• Separating a form for use in various departments

Hold module

DESCRIPTION
This module will hold an entity in a queue to wait for a signal, wait for
a specified condi- tion to become true (scan), or be held infinitely (to
be removed later with the Remove module).

If the entity is holding for a signal, the Signal module is used elsewhere in
the model to allow the entity to move on to the next module. If the entity is
holding for a given condi- tion to be true, the entity will remain at the
module (either in a defined or internal queue) until the condition(s)
becomes true. When the entity is in an infinite hold, the Remove module is
used elsewhere in the model to allow the entity to continue processing.
 TYPICAL USES
• Waiting for a traffic light to turn green

• Holding a part for authorization

• Checking the status of a machine or operator to continue a process

Match module
DESCRIPTION
The Match module brings together a specified number of entities waiting
in different queues. The match may be accomplished when there is at least
one entity in each of the desired queues. Additionally, an attribute may be
specified such that the entities waiting in the queues must have the same
attribute values before the match is initiated.

When an entity arrives at the Match module, it is placed in one of up to

five associated queues, based on the entry point to which it is
connected. Entities will remain in their respective queues until a match
exists.

Once a match exists, one entity from each queue is released to be

matched. The matched entities are then synchronized to depart from
the module.

TYPICAL USES
• Assembling a part

• Gathering various products for a customer order

• Synchronizing a customer exit with a filled order

Pickup module
DESCRIPTION
The Pickup module removes a number of consecutive entities from a
given queue starting at a specified rank in the queue. The entities that
are picked up are added to the end of the incoming entity’s group.

TYPICAL USES
• Gathering an order from various queue
locations

• Gathering completed forms for an office

order

• Picking up students at a bus stop for school

ReadWrite module

DESCRIPTION
The ReadWrite module is used to read data from an input file or the
keyboard and assign the data values to a list of variables or attributes
(or other expression). This module is also used to write data to an
output device, such as the screen or a file.

When reading from or writing to a file, the ReadWrite logic varies

according to the
Type of Arena File Name (the Access Type of a file is specified in the
File module).

Sequential File or LOTUS Spreadsheet Access Types. When an

entity arrives at the ReadWrite module, the specified file is examined
to see if it is open (active). If not, the file is automatically opened. The
values of the attributes, variables, or expressions (other) listed are read
or written according to the format specified.

If you plan to import Lotus (.wks) files into Excel, see Lotus 1-2-3
Release 1.x (WKS) Format for guidelines.
Microsoft Excel, Microsoft Access, and ActiveX Data Objects Access
Types. When an entity arrives at the ReadWrite module, the specified file
is examined to see if an ADO connection to the file is open (active). If the
file is currently closed, then an ADO connection is automatically opened
to the data source using either the
Microsoft Jet OLE DB Provider (if the Access Type is Microsoft Excel
or Microsoft Access) or the specified connection string (if the Access
Type is ActiveX Data Objects).

The Recordset ID is then examined to see if that recordset in the file is

open. A recordset refers to a table of data in the data store that is
organized in columns (i.e., fields) and rows (i.e., records).

If the recordset is currently closed, then it is automatically opened using

the recordset definition specified in the File module (e.g., the specified
named range or table name). The recordset then remains open until the
file is closed.

The values of the attributes, variables, or expressions (other) listed in

the
Assignments repeat group are then read from or written to the specified
Record Number (i.e., row) in the recordset. The first entry in
Assignments is read from or written to the first field in the record, the
second entry corresponds to the second field, and so on.

Extensible Markup Language Access Type. When an entity arrives at

the Read- Write module, the specified file is examined to see if it is
open (active). If not, the file is automatically opened into a single ADO
recordset.

The values of the attributes, variables, or expressions (other) listed are then
read from or written to the specified Record Number (i.e., row) in the
recordset.

TYPICAL USES
• Reading in airline arrival/departure information

• Prompting an end user for model configuration data

(menu)

• Writing order information to a data file, such as

order arrival, order fill time, order completion time
Release module

DESCRIPTION
The Release module is used to release units of a resource that an entity
previously has seized. This module may be used to release individual
resources or may be used to release resources within a set. For each
resource to be released, the name and quantity to release are specified.

When the entity enters the Release module, it gives up control of the specified
resource(s). Any entities waiting in queues for those resources will gain
control of the resources immediately.

TYPICAL USES
• Finishing a customer order (release the
operator)

• Completing a tax return (release the

accountant)

• Leaving the hospital (release the doctor,

nurse, hospital room)

Remove module

DESCRIPTION
The Remove module removes a single entity from a specified position in a
queue and sends it to a designated module.

When an entity arrives at a Remove module, it removes the entity from the
specified queue and sends it to the connected module. The rank of the
entity signifies the location of the entity within the queue. The entity that
caused the removal proceeds to the next module specified and is processed
before the removed entity.

TYPICAL USES
• Removing an order from a queue that is due to be completed next

• Calling a patient from a waiting room for an examination

• Retrieving the next order to be processed from a pile of documents

Seize module

DESCRIPTION
The Seize module allocates units of one or more resources to an entity.
The Seize module may be used to seize units of a particular resource, a
member of a resource set, or a resource as defined by an alternative
method, such as an attribute or expression.

When an entity enters this module, it waits in a queue (if specified) until all
specified resources are available simultaneously. Allocation type for resource
usage is also specified.

TYPICAL USES
• Beginning a customer order (seize the
operator)

• Starting a tax return (seize the accountant)

• Being admitted to hospital (seize the

hospital room, nurse, doctor)

Search module

DESCRIPTION
The Search module searches a queue, a group (batch), or an expression to
find the entity rank (for entities in a queue or group) or the value of the
global variable J that satisfies the specified search condition. When
searching a queue or group, the value of the global system variable J is set
to the rank of the first entity that satisfies Search Condition, or to 0 if
Search Condition is not satisfied. When searching an expression, the
global system variable J is set to the value of the first index value that
satisfies the search condition or to zero if no value of J in the specified
range satisfies the search condition.

When an entity arrives at a Search module, the index J is set to the starting
index and the search condition is then checked. If the search condition is
satisfied, the search ends and the current value of J is retained. Otherwise,
the value of J is increased or decreased and the condition is rechecked.
This process repeats until the search condition is satisfied or the ending
value is reached. If the condition is not met or there are no entities in the
queue or group, J is set equal to 0.

TYPICAL USES
• Looking for a particular order number in a
queue

• Searching a group for a certain part type

• Determining which process to enter based

on availability of resources (search an
expression)

Signal module

DESCRIPTION
The Signal module sends a signal value to each Hold module in the model
set to Wait for Signal and releases the maximum specified number of
entities.

When an entity arrives at a Signal module, the signal is evaluated and the
signal code is sent. At this time, entities at Hold modules that are waiting
for the same signal are removed from their queues. The entity sending the
signal continues processing until it encounters a delay, enters a queue, or is
disposed.

TYPICAL USES
• Analyzing traffic patterns at an intersection (signal
when the light turns green)

• Signaling an operator to complete an order that was

waiting for a component part
Store module

DESCRIPTION
The Store module adds an entity to storage. The Unstore module may then be
used to remove the entity from the storage.

When an entity arrives at the Store module, the storage specified is

incremented, and the entity immediately moves to the next module in the
model.

Storages are useful for displaying entity animation while an entity

undergoes processing in other modules. Additionally, statistics may be
kept on the number of entities in storage.

TYPICAL USES
• Animating a part through a number of delay operations
(load, setup, process, unload)

Tracking the number of customers within a grocery store (place in

storage upon entry)

Unstore module

DESCRIPTION
The Unstore module removes an entity from storage. When an entity
arrives at the Unstore module, the storage specified is decreased and the
entity immediately moves to the next module in the model.

TYPICAL USES
• Removing the entity from an animation location
when processing is complete
 • Tracking the number of customers within a grocery
store (unstore upon exit)

Adjust Variable module

DESCRIPTION
The Adjust Variable module adjusts a variable to a target value at a
specified rate.
This module might be used with the Rotate By Expression option in
Global and Resource pictures to present smooth animated rotations of
pictures. It might also be used to approximate/ animate a continuous
increase or decrease to a variable value over time.

When an entity enters an Adjust Variable module, the Variable Name is

adjusted to the To Value at the specified Rate. The entity is held in the
module until the adjustment is completed.

The Update Interval specifies the time interval between actual assignment
updates of the variable value over the time period of the change. A smaller
update interval produces smoother animation in plots or rotating pictures
that reference the variable, as well as more accurate time-persistent
statistics collected on the variable. A larger update interval produces faster
run speeds.

TYPICAL USES
• Rotate a resource picture to 180 degrees at a
rate of 5 degrees per second
EXPERIMENT-7

AIM: Study assembly module on ProE software.

STUDY: This study presents the modules included on the assembly on

Pro-E CAD software.

ASSEMBLY MODELING
Mostly the designs consist of more than one component that are
assembled together at their relative working positions. These assembly
designs are created in the Assembly mode of Pro/ENGINEER. To
proceed to the assembly mode, choose the Create a new object button
from the Top Toolchest. The New dialog box is displayed, select the
Assembly radio button from the Type area and then select the Design
radio button from the Sub-type area as shown in Figure -1. Specify the
name of the assembly in the Name edit box and choose OK.

Figure 9-1 Selecting the Assembly mode from the New dialog box
ASSEMBLY DATUM PLANES

When we enter the assembly environment, the three default assembly

datum planes are displayed on the graphics screen. If you do not want
the assembly datum planes to be displayed then while opening a new
file you need to clear the Use default template check box. Generally,
it is advised to use the assembly datum planes as the first feature of the
assembly and then assemble the components of the assembly taking the
reference of these assembly datum planes. Using the datum planes as
the first feature helps you during the modification of the assembly.
Some of the advantages of using the assembly datum planes are: the
components of the assembly can be redefined in such a way that the
components placed later can be made the first component, the first
component can be replaced by some other component, and the
placement constraint of the first component can be modified.

ASSEMBLING THE COMPONENTS

The components in the assembly can be placed parametrically or
nonparametrically. If the components are placed using the placement
constraints, it is called parametric assembly and if the components are
packaged, it is called nonparametric assembly.

To assemble the components parametrically, choose ASSEMBLY >

Component > Assemble. The Open dialog box is displayed. Once you
select the part to assemble from the Open dialog box, the Component
Placement dialog box will be displayed as shown in Figure 2.

Figure 2 The Place tab of the Component Placement dialog box

The Component Placement dialog box has multiple functions. This
dialog box is used for both constrained and packaged placement of
components. There are two tabs in this dialog box, the Place tab and
the Move tab. The options under these tabs are discussed next.
EXPERIMENT-8

AIM: Simulate movement of cam and follower mechanism on ProE

software.

REQUIRED COMPONENTS: Before doing Simulation, we need to

have all the parts and required components for Assembly. Assembly
will comprise of-

1. cam_follower.asm—an assembly comprised of a cam and a

roller follower
2. base.prt—the ground body, comprised of two parts (blue)
3. cam.prt—a rounded, elongated solid with flat faces (purple)
4. roller.prt—a wheel with flat faces with that serves as the
second cam (green)
5. follower.prt—a holder for the roller (brown)
6. follower.asm—a subassembly connecting roller.prt and
follower.prt with a pin joint

This is what will be made and then simulated

Procedure:
Part-A: Make the requisite Assembly using

following steps: 1. Make this cam

2. Cam ground

3. Cam support rod

4. Damper cylinder

5. Follower fork
6. Follower round

7. Follower shaft
8. Spring

Part-B: Making of Assembly & Simulation as:

1. New assembly>> make the ground at default>> do not start from

cam.
2. Assemble the shaft( mate – surface and align the axis)

3. Cam connection – is cylindrical

4. Mechanism>> drag>> pick cam>> mouse. Mouse un pressed –
cam should rotate

5. Assemble>> follower fork >> align axis, align datums at least

2>> connection - cylindrical
6. Get this >> try mechanism and drag to check 1- DOF
 7. Completely constrain shaft and then the round
8. Assemble spring>> align, the datums, then mate another datum
to the fork
9. Mechanism>> drag
Note (at this level, pro E will tell if there is any connection not
defined. Check the components used to define align and mate
features. It should be immediate parent.) Redefine accordingly.
10.Modify block2 and make datums as shown

11. Make datums on cylinder _damper , to align the block2>> mate

the surfaces ( bring them closer to avoid rotational problems)
12. New assembly>> assemble asm1 at default.
13. Assemble follower _ cam assembly >> align these datums
14. Align other datum and then the bottom planes. ( Note- here a
value of 3.0691, was taken to ensure that cam co-insides with
roller. Used measure command after aligning the cam and roller
to know this value).
15. Check drag command there is no error of connection not
defined.
16.Mechanism>> models>> cams>>new

17. Automatic>> select all the surfaces one by one – use query
select.

18. Done>>cam 2
19. Query select surface of round
20. Done >> ok
21.A cam connection has been made

22. Drag>> check that the mechanism is moving with this

connection

23.Create snap shots>> close >> save

24. Now we can use the display icon to see these snap shots.

RESULT: Simulation for movement of cam and follower

mechanism is performed.
Arena Simulation Viva-Voce Questions and Answers
1. What Is Simulation?
Answer :

Simulation is the imitation of some real thing, state of affairs or process. In health
professions education, simulation is a methodology to help achieve educational
goals. Healthcare simulation encompasses a range of activities that share a broad but
common purpose: To improve the safety, effectiveness and efficiency of healthcare
services.

2. What Is A Simulationist?
Answer :

A simulationist is an expert in the knowledge, skills and attitudinal aspects of using

the methodologies of simulation to achieve learning objectives.

3. What Is A Simulation Centre?

Answer :

A simulation centre is a physical space where simulation is employed for health

professions education. Simulation activities can include technical skills training
(manikins, task trainers), role playing, virtual reality/e-learning and blended
simulation.

4. What Is The Need For Simulation?

Answer :

The Need for Simulation :

A simulator is a collection of hardware and software systems which are used to

mimic the behaviour of some entity or phenomenon. Typically, the entity or
phenomenon being simulated is from the domain of the tangible ranging from the
operation of integrated circuits to behaviour of a light aircraft during wind sheer.

Simulators may also be used to analyze and verify theoretical models which may
be too difficult to grasp from a purely conceptual level. Such phenomenon range
from examination of black holes to the study of highly abstract models of
computation. As such, simulators provide a crucial role in both industry and
academia.

Despite the increasing recognition of simulators as a viable and necessary research

tool, one must constantly be aware of the potential problems which simulators may
introduce. Many of the problems are related to the computational limitations of
existing hardware platforms but are quickly being overcome as more powerful
platforms are introduced. Other problems, unfortunately, are inherent within
simulators and are related to the complexity associated with the systems being
simulated.

5. What Is The Classification Of Simulation Systems?

Answer :

It is useful to classify the system being simulated into two separate categories
depending upon the degree of randomness associated with the behaviour of the
system in its simulated environment.

For example, consider a simulated system consisting of a series of bank tellers who
must provide transaction services to incoming customers. The length of time
required for a teller to process a customer's transaction cannot usually be
predetermined before the simulation is started. Consequently such a simulation
system must introduce random behaviour to simulate the duration of each
transaction.

During the analysis of a real world banking system it may be discovered that the
time required for a transaction occurs over some well known probability
distribution. Hence the duration of each transaction may be generated from this
distribution. A similar strategy may be adopted for the rate at which customers
enter a bank. Through the introduction of this randomness, the results of a
simulation may never be the same as a previous simulation.

A system, such as this one, that relies heavily upon random behaviour is referred to
as a stochastic system. The results generated from a stochastic system are typically
analyzed statistically in order to make conclusions regarding the behaviour of the
system.

Conversely, a deterministic simulation system incorporates absolutely no random

behaviour whatsoever. As such, the simulation results for a given set of inputs will
always be identical. Simulations involving circuit behaviour are examples of
deterministic systems.

Supplying high signals to both inputs of a 2-input NAND gate will always produce
a low signal on the gate's output, regardless of where the gate is located in the
circuit's design hierarchy or when the inputs are received by the gate. In the
context of circuit simulation, deterministic simulation is used to verify that a
particular circuit design is behaving as expected when the circuit is supplied with
a given set of inputs, the circuit produces the expected outputs at the correct time.
Although this report will focus primarily upon deterministic simulation systems,
stochastic systems can also be simulated with modest modifications to the
implementation.

6. What Are Simulation Models?

Answer :
Simulation Models : During the design and implementation of a simulator,
various techniques and strategies may be adopted to model the behaviour of a
given system. Depending upon the system to be simulated, some techniques may
be more favourable than others. Factors including the level of abstraction and the
desired accuracy and speed of the simulation should be taken into consideration
when designing the simulator engine. Traditionally, simulators are designed using
either continuous or discrete-event techniques to simulate a given system.

7. What Are The Abstraction Levels For Circuit Simulation?

Answer :

Abstraction Levels for Circuit Simulation : This report will describe the design
and implementation of a digital circuit simulator. Consequently, this section will
outline some of the aspects related to the simulation of circuits, including the
different levels at which circuit simulators may operate.

Circuit simulation provides a means of modelling a circuit's response to a given set

of inputs. The simulator may generate numbers representing the voltages present at
specific nodes of the circuit at certain times or it may generate waveform diagrams
that show the circuit's output over the duration of the simulation. What is actually
produced as a result of the simulation is largely dependent upon the abstraction
level at which the circuit was described and subsequently simulated.

For example, simulating a circuit described in terms of transistors and capacitors

will conventionally show how these components interact at the electrical or analog
level, whereas simulating a circuit described in terms of gates, flip-flops and
registers will demonstrate the digital interaction amongst the components.

Circuits may be described and simulated at several levels of abstraction. This

section will describe three major abstraction levels, each of which are related to the
simulation models described above. These levels are described below in order of
increasing abstraction level.

8. What Are Circuit-level Simulators?

Answer :

Circuit-level simulators : Circuit-level simulators are used to model the behaviour

of a circuit at its lowest conceptual level. The circuit is described in terms of
transistors, wires, capacitors and resistors and their respective interconnectivity.
Circuit-level simulators manipulate extensive detail regarding the interaction of all
the components in the circuit and also take into consideration subtleties such as
wire resistance and geometric properties of the subcomponents.

The end goal circuit level simulation is to produce very detailed analog waveforms
which accurately model the behaviour of the circuit's devices in the real world.
Consequently, continuous simulation techniques are often used to implement
circuit-level simulators.

Circuit-level simulations are typically performed in several stages. During the first
stage, referred to as node-extraction, static analysis of the circuit description is
performed. From this analysis, information regarding the circuit's devices, their
respective attributes and their connectivity is obtained. This information is
subsequently combined with modules known as device models that describe the
behaviour of each device on a mathematical level. In order to model the circuit's
behaviour, the simulator must then solve a system of differential linear equations
which is derived from all the information supplied to it during the node-extraction
phase.

Although this method generates very accurate results, the technique is very
computationally intensive, resulting in poor simulation speed. As a result, circuit-
level simulation is usually not feasible for large designs and is therefore commonly
used to simulate only the most critical subregions of a given circuit.

9. What Are Logical Level Simulators?

Answer :

Logic-level Simulators : Logic-level simulators attempt to remedy the

computationally intensive nature of circuit-level simulators by raising the level of
abstraction to the domain of switches and logic components. Instead of
manipulating continuous, analog data, logic-level simulators simply process logic
values; that is, 0, 1 and X. In addition, logic-level simulators traditionally simplify
the simulation process by assuming that the connecting wires have negligible
resistance.

Logic level simulators can be subdivided into two further categories, switchlevel
and gate-level simulators. In switch-level simulators, transistors are promoted to
elementary switches and very little attention is given to the intricacies of other
transistor attributes. During the simulation itself, equations governing the
behaviour of the circuit are greatly approximated, thereby increasing the speed at
which the simulator operates. The detail that is inevitably lost as a result of this
approach is not usually vital.

Gate-level simulators operate at yet a higher abstraction level. Low level circuit
devices such as transistors, capacitors and resistors are replaced with logic gates
such as NAND, XOR and flip-flops. Circuits described at this level bear strong
resemblance to data flow diagrams in which information is passed amongst
interconnected components.

Effective use of logic gates permit relatively high-level designs to be easily

described and subsequently simulated. Because the components are increasingly
abstract, more complex systems may be designed and simulated at the gate level
rather than at the switch level. Traditional gate-level simulators are implemented
using discrete-event simulation; as such, this report will primarily focus upon
circuits described at the gate level.

There have been several successful attempts to merge switch-level simulators with
simulators that operate at the gate-level and above, thereby allowing the designer
to have the flexibility and speed of high-level simulators, while at the same time
retaining some of the accuracy associated with switch-level simulators.

10. What Are Functional- And Behavioural-level Simulators?

Answer :

Functional- and Behavioural-level Simulators : Functional- and

behaviourallevel description languages and simulators represent the highest levels
of simulation available to circuit designers. These levels enable designers to model
circuits in terms of interacting abstract units that may not even be capable of
fabrication.

As such, designers are not limited by the restricted behaviour of fundamental

circuit devices. In addition, these levels also provide designers a viable means of
quickly exploring alternatives without becoming overwhelmed with the impact that
design decisions would have on the circuit at lower levels.

Functional-level simulators are generally closer to the actual hardware

representation than behaviour-level simulators. An abstract unit in a functionallevel
simulation would accept input and produce output just like its corresponding
hardware component.

However, more flexibility is permitted with respect to how the input is presented to
the unit and how it is processed to produce output. For example, an adder at the
gate-level may consist of several half-adders which adds to numbers by operating
directly on their bits. The equivalent functional-level unit would simply take two
integers and add them using arithmetic constructs available in the hardware
description language.

Behavioural-level simulators go one level higher and permit designers to model

abstract control processing which may not be realizable in hardware. The purpose
of these simulators is to give the designer a general overview of the design and to
experiment with high-level alternatives. The usefulness of design tools and
simulators that operate at this level has been the subject of debate due to the
difficulty in translating such high level designs into compact, highperformance
circuits.

However, advances in silicon compilation have made the translation process easier
and more efficient. In addition, high level simulators are still useful for rapid
prototyping, even if the design is not actually physically fabricated. Rapid
prototyping allow designers to study the feasibility of a high level design before
actually delving into the tedious, low-level details such as placement and routing.
 11. Explain The Simulator User Interface?
Answer :

The Simulator User Interface : The intuitiveness and robustness of the user interface
used by a software application can strongly influence the productivity of the people
using that application. This chapter focuses on the design and operation of a
graphical user interface for a digital simulator engine. Details with respect to the
chosen platform and implementation language will also be discussed and justified.
In addition, some limitations of the GUI will be described and potential solutions to
these restrictions will be presented.

12. What Are The Advantages And Disadvantages Of Simulation?

Answer :

Advantages of Simulation :

One of the primary advantages of simulators is that they are able to provide users
with practical feedback when designing real world systems. This allows the
designer to determine the correctness and efficiency of a design before the system
is actually constructed. Consequently, the user may explore the merits of
alternative designs without actually physically building the systems. By
investigating the effects of specific design decisions during the design phase rather
than the construction phase, the overall cost of building the system diminishes
significantly.

Another benefit of simulators is that they permit system designers to study a

problem at several different levels of abstraction. By approaching a system at a
higher level of abstraction, the designer is better able to understand the behaviours
and interactions of all the high level components within the system and is therefore
better equipped to counteract the complexity of the overall system. This
complexity may simply overwhelm the designer if the problem had been
approached from a lower level.

Thirdly, simulators can be used as an effective means for teaching or

demonstrating concepts to students. This is particularly true of simulators that
make intelligent use of computer graphics and animation. Such simulators
dynamically show the behaviour and relationship of all the simulated system's
components, thereby providing the user with a meaningful understanding of the
system's nature. Consider again, for example, a circuit simulator.

Disadvantages of Simulation :

Despite the advantages of simulation presented above, simulators, like most tools,
do have their drawbacks. Many of these problems can be attributed to the
computationally intensive processing required by some simulators. As a
consequence, the results of the simulation may not be readily available after the
 simulation has started -- an event that may occur instantaneously in the real world
may actually take hours to mimic in a simulated environment.

One of the ways of combating the aforementioned complexity is to introduce

simplifying assumptions or heuristics into the simulator engine. While this
technique can dramatically reduce the simulation time, it may also give its users a
false sense of security regarding the accuracy of the simulation results.

Another means of dealing with the computational complexity is to employ the

hierarchical approach to design and simulation so as to permit the designer to
operate at a higher level of design. However, this technique may introduce its own
problems as well. By operating at too high an abstraction level, the designer may
tend to oversimplify or even omit some of the lower level details of the system. If
the level of abstraction is too high, then it may be impossible to actually build the
device physically due to the lack of sufficiently detailed information within the
design.

13. Explain Continuous Simulation?

Answer :

Continuous Simulation : Continuous simulators are characterized by the extensive

use of mathematical formulae which describe how a simulated component responds
when subjected to various conditions. For example, consider a circuit described at
the transistor, resistor and capacitor level. The behaviour of all these components are
well understood and are governed by several equations which describe their
respective behaviours.

A continuous simulator would apply those equations in the context of the

components' environment and connectivity and produce a continuous graph which
accurately reflects how the components would react if they were actually hooked
up in reality. The graphs usually reflect the changes in the state of the system with
respect to time; however, other relationships may also be demonstrated as well.
Unfortunately, the mathematical equations employed by a continuous simulator
can make the simulation very computationally intensive, especially in the presence
of thousands of interconnected elements. As such, continuous simulators may be
slow and are consequently only useful when simulating a relatively small number
of components which are described at a low level of abstraction.

14. Explain Discrete-event Simulation?

Answer :
Discrete-Event Simulation : Discrete-event simulation is used to simulate
components which normally operate at a higher level of abstraction than
components simulated by continuous simulators. Within the context of
discreteevent simulation, an event is defined as an incident which causes the
system to change its state in some way. For example, a new event is created
whenever a simulation component generates output.

A succession of these events provide an effective dynamic model of the system

being simulated. What separates discrete-event simulation from continuous
simulation is the fact that the events in a discrete-event simulator can occur only
during a distinct unit of time during the simulation -- events are not permitted to
occur in between time units. Discrete event simulation is generally more popular
than continuous simulation because it is usually faster while also providing a
reasonably accurate approximation of a system's behaviour.

15. What Are The Windows In Simulator GUI?

Answer : The simulator GUI employs two windows the circuit editor window (also
known as the main window) and the signal display window. Together, these two
windows provide the necessary functionality which lets the user construct and
simulate digital circuits.

16. List Some Open Source Circuit Simulator Software List?

Answer :

some open source circuit simulator software list:

Micro-Cap 10 – is another demo version circuit analyzer and simulator from

Spectrum Soft. As they claim its a mixed mode digital/analog circuit simulator
with an intuitive user interface, fast simulation and great performance. I haven’t
tried this yet, so if you are interested try your own.

PECS – is a free power electronics circuit simulator created by Richard Tymerski.

You can download the various manuals and tutorials from the website before start
using the simulation tool.

Proteus – Prospice is a mixed mode, Spice based simulation tool from LabCenter.
They have two versions, basic and advanced. Basic version is free which supports
interactive simulation only while advanced supports a range of useful functions
and features like graph based analysis which includes frequency, noise, distortion,
fourier parameters etc.

QUCS – Quite Universal Circuit Simulator is a free simulation software developed

on GNU/Linux environment. Well this software really works on other operating
systems such as Solaris, Apple Macintosh, Microsoft windows, FreeBSD, NetBSD
etc. User can simulate large signal, small signal and noise behavior of the circuit
using this simple circuit simulator.
Solve Elec – is an electrical circuit simulator (free version) which is developed for
Macintosh OS and Windows. It enables users to draw and analyse circuits (both
electrical and electronic) functioning in direct current or alternating current, get
formulas, verify equations, get equivalent circuits etc.

XSpice – is developed as an extension to Spice 3 by Georgia Institute of

Technology. It has code modelling feature which enables user to add new models.

MultiSim – is a student version circuit simulation software from National

instruments. As you know, student versions always comes with limited access. Still
this is a great simulation tool for beginners in electronics. MultiSim, the circuit
maker software enables you to capture circuits, create layouts, analyse circuits and
simulation. Highlight features include exploring breadboard in 3D before lab
assignment submission, create printed circuit boards (PCB) etc. Breadboard
simulation is possible with Multisim circuit simulator.

TopSpice – this is a demo version circuit simulator from Penzar. This electronic
simulation tool is tailored to work with Windows only and its is compatible for
Windows XP/Vista/7. TopSpice is a mixed mode mixed signal digital,analog,
behavioral simulation software. It offers both Pspice and Hspice compatible
simulation of circuits.

Circuit Simulator 1.5j – is a freeware circuit simulation tool. I have not used this
tool or even attempted a try. I add this as a suggestion from a user in our forum. I
think this is just basic tool with very basic functions, created for starter purpose.
Use at your own risk.

MacSpice – is a free circuit simulation software for Apple Macintosh users. This
circuit simulation which is compatible for PowerPC and Intel architecture Apple
Macintosh (MAC pc) computers is derived from Berkeley Spice 3f5 . This
breadboard simulator can perform simulation ranging from a single resistor to an
integrated circuit with thousands of devices and components packed together.

5Spice – is a free analog circuit analysis and simulator with many great features
which includes a user expandable library of Spice/Pspice models, save any number
of analysis results, integrated graphing of simulation results, student level
MOSFET IC design etc. The focus is emphasized on analog circuit analysis and
design at component level. 5Spice is mainly designed for students and educators,
rather than industry professionals. Latest version of 5spice is released on October
31st 2001 – v 1.65.

NgSpice – one of the popular and widely used free, open source circuit simulator
from Sourceforge. NgSpice is developed by a collective effort from its users and
its code is based on 3 open source software packages:- known as:- Spice3f5 , Cider
and Xspice. Ngspice is a part of gEDA project which is growing every day with
suggestions from its users, development from its contributors, fixing bugs and
approaching perfection. As its a collaborative project you can suggest
improvement of the circuit simulator and be a part of the development team.

GnuCap – is another open source project, developed as a general purpose circuit

simulator. Known widely as GNU Circuit analysis package, this linux based circuit
simulator performs various circuit analysis functions as dc and transient analysis,
ac analysis etc. Developers have incorporated spice compatible model for
MOSFET, BJT and Diode.

CircuitLogix – this student version software from CircuitLogix enables you to

perform analog, digital and mixed mode circuit analysis and simulation. This
SPICE simulation software provides 4000 devices on its student version which is
1/3 of the pro version. This circuit building software give access to switches, linear
IC and digital IC, FET, Transistors, relays, displays, signal generators, SCR’s, opto
isolators, photo diodes, semiconductors, motors etc.

LTSpice – is a widely popular SPICE simulator from Linear. LTspice is a free

circuit simulation tool from Linear Technology corporation. This simulation
software is considered as one of the best freeware available. Highlight of LTspice
is much fast simulation of switching regulators with enhanced SPICE (compared to
normal SPICE simulators).LTspice gives access to over 200 op amp models,
transistor models, MOSFET models etc. A high disadvantage of LTspice is its
proprietary code base which is licensed by Linear Technology. Had they made it
open source, LTspice could have gone places with collaborative development.

17. Can I Use The Simulator Software Online With Just My Web Browser?

Answer :

No. The simulators are desktop applications that must be installed on your PC and
used with simulator controls that are connected to the same PC. Only in this way
can they deliver the real-time performance that's required to simulate the behaviour
of real heavy equipment.