![](bg6.png)
SPN for further analysis. The icon bar on the bot-
tom of the screen includes following modeling ele-
ments: mode select, simple state, initial, join, and
choice pseudostates, state transition, and element Im-
port. The last one can be used to set the operational
model linked to the current application model.
The TimeNET window while working in the net
class eSMoper looks similar with two exceptions: The
section eSMoper of the menu panel does not let the
user create an SPN out of the operational model, and
the icon bar at the bottom of the screen does not in-
clude the element Import. The reason for this is that
one operational model can be linked to numerous ap-
plication models.
Figure 3: Elements for creating an application model.
Elements which can be used for creating an appli-
cation model are shown in Fig. 3. A simple state is
represented by an empty rectangle with rounded cor-
ners. The initial pseudostate is depicted as a small
solid black circle. The join pseudostate is shown as
a small solid black rectangle with a letter J above it,
while the choice pseudostate is depicted as an empty
rhombus. Transitions are displayed as an arrow di-
rected from the outgoing state to the incoming state.
The Import specification is represented by an empty
rectangle with standard sharp corners. Inside the fig-
ure, there is a word Import with a semicolon and
the name of the file containing the operational model
linked to the current application model.
By selecting a simple state in the selection mode,
the user can add attributes and change its name in
the panel at the right side of the screen (see Fig. 1).
Initially, each simple state gets a name which con-
sists of the word ”state” and an ordinal number be-
ginning from zero automatically. The user has the
opportunity to change the name in the property text.
The property stereotype is being used for adding at-
tributes to the element. This field can be filled up
automatically by using the fields below. The stereo-
typelist demonstrates all the attributes added to the
chosen state. In the field Choose stereotype, the
user can choose between <<ResourceUsage>> and
<<GaStep>> stereotypes. Depending on the choice
in this field, the field Choose TAG offers to state
either execution time in the attribute execTime (in
the case of the <<ResourceUsage>> stereotype) or
the state probability in the attribute prob (stereotype
<<GaStep>>). By creating an operational model,
the attribute powerPeak of the <<ResourceUsage>>
stereotype is also available for stating the power con-
sumption of the simple state. This attribute is not
available in the application model as it is stipulated
by the method described in Sec. 2. Table 1 gives an
overview of the attributes which can or must be used
in both models. In the text field Set Value, the user
states a value of the chosen attribute. By clicking
the button Add Stereotype, the chosen attribute will
be added to the stereotype list above. The further but-
tons Remove and Remove all let the user delete either
a single chosen attribute or all of them, respectively.
The element Import has an additional property
field filename, which is used to set the name of the
XML file containing the corresponding operational
model.
After creating both operational and application
model, the user can start the transformation to a Petri
net via the menu item eSMapp → eSMapp to eDSPN.
TimeNET will ask for the name of the resulting XML
file to save the results. After the transformation,
the created file containing a new eDSPN should be
opened and the stationary analysis (menu Evaluation)
started. The results will be displayed in the field mea-
sure in the TimeNET workspace. The value gives an
estimation of the system power consumption.
4 EXAMPLE
In this section, we show how the possibilities of the
presented TimeNET extension are used in practice.
In comparison to the example given in (Shorin et al.,
2012), we explicitly take not an embedded, but an
industrial control system to show the breadth of the
method and software application. In this example, we
consider component production by a workbench with
a main and two reserve motors. Its structure is de-
picted in Fig. 4.
The workbench gets its first order and is being
started (represented by the state Start). The process
goes through the fictitious state Continue (see details
below) and the order is adapted. Furthermore, there
are three possibilities of producing components de-
pending on performance requirements. The first one
is called Slow production — it takes 5 minutes to cre-
ate one unit. By choosing the second mode, one mo-
tor more is started and thus, the production speed re-
duces to 3 minutes. The third possibility is to start
two reserve motors and to produce the component in
only one minute. The fastest way could be the most
preferable one, but the difference between these three
modes is also in the power consumption. We assume
that the longer it takes the workbench to produce a
SIMULTECH2014-4thInternationalConferenceonSimulationandModelingMethodologies,Technologiesand
Applications
88