<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>From Work Practice Models and Simulation To Implementation of Human-Centered Agent Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Maarten Sierhuis</string-name>
          <email>msierhuis@mail.arc.nasa.gov</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>William J. Clancey</string-name>
          <email>bclancey@mail.arc.nasa.gov</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mike Scott</string-name>
          <email>mscott@ptolemy.arc.nasa.gov</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>NASA/Ames Research Center Computational Sciences Mail Stop</institution>
          <addr-line>269-3 Moffett Field, CA 90435 USA (</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>QSS NASA/Ames Research Center Mail Stop</institution>
          <addr-line>269-3 Moffett Field, CA 90435 USA (</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>RIACS/USRA NASA/Ames Research Center Mail Stop</institution>
          <addr-line>19-39 Moffett Field, CA 90435 USA (</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>1993</year>
      </pub-date>
      <abstract>
        <p>In this paper we describe an agent-based software development environment for developing agent systems that are fundamentally based on a holistic analysis of the human and software agent organization and work practices for which the agent system is to be developed. Brahms is an agent modeling, simulation and development environment developed at NASA Ames Research Center. Brahms stems from a decade of research on modeling and simulating human work practices. As a result of this research, partly at NASA Ames and partly in industry, we are now working on extending the environment to allow for the design and implementation of software systems that are fundamentally based on work practice and include software agents that have a dynamic representation of the human- and software agents it is collaborating with.</p>
      </abstract>
      <kwd-group>
        <kwd>multi-agent</kwd>
        <kwd>modeling</kwd>
        <kwd>simulation</kwd>
        <kwd>intelligent agents</kwd>
        <kwd>work practice</kwd>
        <kwd>activity</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1. Modeling and simulating work practice</p>
      <p>Work practice is a concept that originates in socio-technical
systems, business anthropology, work systems design, and
management science.</p>
      <p>
        The notion of “practice” is central to work systems design,
which has its roots in the design of socio-technical systems, a
method developed in the 1950s by Eric Trist and Fred Emery [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
Socio-technical systems design sought to analyze the relationship
of the social system and the technical system, such as
manufacturing machinery, and then design a “socio-technical
system” that leveraged the advantages of each. Work systems
design extends this tradition by focusing on both the formal
features of work (explicit, intentional) and the informal features
of work (as it is actually carried out “in practice,” analyzed with
the use of ethnographic techniques) [2] [3] [4] [5, chapter 16].
      </p>
      <p>A work practice is defined as the collective activities of a
group of people who collaborate and communicate, while
performing these activities synchronously or asynchronously.
Most often, people view work merely as the process of
transforming input to output, i.e. a Tayloristic view of work. For
example, when building a house the input and output of the work
is well defined. Sometimes however, it is more difficult to
describe the input and output of the work. For example, consider
a soccer match between two professional soccer teams. It is
difficult to define the input and output of this type of work,
although most of us would agree that professional soccer players
are working. To describe the work of a soccer team we quickly
fall into descriptions about teamwork and collaboration on the
field.</p>
      <p>We claim that the individual activities that make up the work
not only have to do with the transformation of input to output, but
more importantly with the collaboration between individuals in
action, in pursuit of a goal. Imagine soccer players who
collaborate in their activities of kicking a soccer ball, in pursuit of
scoring a goal. Just focusing on the in- and output of each
individual activity of a soccer player would not only be very
difficult, if not impossible, it would also miss the opportunity to
understand what is really going on in this work. However, in the
past century work has been defined as the transformation of input
to output, starting with Frederick W. Taylor’s view of work to
Michael Hammer’s view of business processes [6].</p>
      <p>We take a different view, and are interested in describing
work as a practice, a collection of psychologically and socially
situated collaborative activities between members of a group. We
try to understand how, when, where, and why collaborative
activities are performed, and identify the effects of these
activities, as well as to understand the reasons why these
activities occur in the way they do. Therefore, the central theme is
to find a representation for modeling work practice. Many
researchers in the social sciences use the word practice as if it is a
well-defined concept that everyone understands. However, it is
difficult to describe what a practice is. People notice when
something is not a practice, and can often describe why. Although
it can be said that a group of people has developed a practice,
when asked to describe what that practice is, and what it consists
of, we find it difficult to describe in words. As such, practice is
part of our tacit knowledge [7].</p>
      <p>An ad hoc definition of the word practice is: The
(collaborative) performance of situated activities in real life
situations, by making use of knowledge previously gained through
experience in performing similar activities.</p>
      <p>In short, practice is doing in action [8]. Scientists have
described how a practice develops, like Wenger, who defines the
creation of a practice as follows [9]:</p>
      <p>Being alive as human beings means that we are constantly
engaged in the pursuit of enterprises of all kinds, from ensuring
our physical survival to seeking the most lofty pleasures. As we
define these enterprises and engage in their pursuit together, we
interact with each other and with the world and we tune our
relations with each other and with the world accordingly. In other
words, we learn. Over time, this collective learning results in
practices, which reflect both the pursuit of our enterprises and the
attendant social relations. These practices are thus the property of
a kind of community created over time by the sustained pursuit of
a shared enterprise.</p>
      <p>Everybody knows what Wenger means when he says, “this
collective learning results in practices”, but what is it that results?
Can it be described? Can it be modeled? To do this we need to be
able to describe practice at an epistemological level we call the
work practice level. In the rest of this paper, we will discuss a
representational language to represent models of work practice.
These models can be simulated in order to show the effects of the
activities of people and their communication, being situated in a
geographical environment, and using tools and artifacts to
perform their collaborative work.</p>
      <p>Work practice includes those aspects of the work process
that make people behave a certain way in a specific situation, at a
specific moment in time, in the real world. To describe people’s
situation-specific behavior we need to include those aspects of the
situation that explain the influence on the activity behavior of
individuals (in contrast with problem-solving behavior), such as
people’s collaboration, “off-task” behaviors, multi-tasking,
interrupted and resumed activities, informal interaction,
knowledge and geography [10] [11].</p>
      <p>Brahms is a modeling and simulation environment for
representing work practice in a rule-based agent language, which
can be simulated using the Brahms rule-based, multi-agent
simulation engine. At NASA we have used Brahms to model and
simulate the work practices of the Apollo astronauts, as well as
the human-robot collaboration for a semi-autonomous robotic
mission to a planetary surface [12] [13] [14].</p>
      <p>To model a work practice we develop seven models, as
described by the World Modeling Framework [15]. First, we
design the Agent Model in which we represent the group-agent
membership hierarchy of all the agents in the work system. The
Agent Model describes to which groups the agents belong and
how these groups are related to each other. After the Agent
Model, the next model that needs to be designed is the Object
Model. In this model we design the class-hierarchy of all the
domain objects and artifacts.</p>
      <p>Now that the agents, objects and real-world artifacts are
represented, the next model is the Geography Model in which the
agents and artifacts are located during the simulation. In Brahms
we model geographical locations using two concepts,
areadefinitions and areas [16]. Area-definitions are user-defined types
of areas. Areas are instances of area-definitions. An area is an
instance of a specific location in the real world that is being
modeled. Furthermore, areas can be part-of other areas. With this
representation scheme we can represent any location at any level
of detail.</p>
      <p>The fourth model is the Activity Model. In the Activity
Model we describe the behavior of agents and objects in terms of
the activities they perform over time. Agent or object activities
are mostly represented at the group-level or class-level
respectively, but can also be represented down at the agent and
object level. Activities at the group- and class-level are inherited
at the lower levels. Related to this, we describe the constraints of
when these activities can be performed in the Timing Model. Such
activity constraints are represented in the form of preconditions of
situation-activity rules. We call such situation-activity rules
workframes [16]. A workframe executes an agent's activity when
its preconditions match against the agent's individual belief-set.
Because activities take time, a workframe instantiation has a
duration. However, activities, and thus workframes, can be
interrupted and resumed, making the actual length of an activity
performance situation dependent.</p>
      <p>Next, we can represent an agent's reasoning behavior as
forward-chaining production-rules in the Knowledge Model. Such
production rules can also be represented at the group-level, and is
also inherited at lower levels. In Brahms, production-rules are
called thoughtframes [16].</p>
      <p>The last model we distinguish is the Communication Model.
In this model we represent the agent and object communication.
In Brahms we represent communication as speech-acts, i.e.
situation-specific communication-actions of agents' beliefs
to/from other agents or artifacts [17].
2. From simulation to agent systems</p>
      <p>We have recently reimplemented the Brahms environment in
Java. As part of this effort we have made three enhancements,
which will allow us to use the Brahms language as a full-fledged
agent language for developing intelligent human-centered
agentbased systems. The first enhancement is the creation of a
realtime Brahms execution engine— the Brahms Virtual Machine
(VM). The VM is similar to the simulation engine, but does not
include time synchronization between agents and objects by a
centralized scheduler. Each agent and object operates
autonomously using its own discrete event engine. This allows
each agent to execute as an independent Java-thread and run as
fast as possible, without having to be synchronized by the
scheduler.</p>
      <p>The second enhancement is a Brahms Java-activity type,
with which a modeler can implement any agent or object activity
in Java. This allows moving execution from a Brahms agent to
Java. The third enhancement is that of a Java-API for the
development of Brahms proxy-agents in Java. Brahms
proxyagents allow moving execution from Java to Brahms.</p>
      <p>L. A. Suchman, Plans and Situated Action: The
Problem of Human Machine Communication.
Cambridge, MA: Cambridge University Press, 1987.</p>
    </sec>
    <sec id="sec-2">
      <title>M. Sierhuis and A. M. Selvin, “Towards a framework</title>
      <p>for collaborative modeling and simulation,” presented
at presented at the Workshop on Strategies for
Collaborative Modeling and Simulation, CSCW '96,
Boston, MA, 1996.</p>
    </sec>
    <sec id="sec-3">
      <title>R. van Hoof and M. Sierhuis, “Brahms Language Reference,”: http://www.agentisolutions.com/documentation/langua ge/ls_title.htm, 2000.</title>
    </sec>
    <sec id="sec-4">
      <title>J. Searle, R., Speech Acts. Cambridge, UK: Cambridge</title>
      <p>University Press, 1969.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>F. E.</given-names>
            <surname>Emery</surname>
          </string-name>
          and
          <string-name>
            <given-names>E. L.</given-names>
            <surname>Trist</surname>
          </string-name>
          , “
          <string-name>
            <surname>Socio-Technical</surname>
            <given-names>Systems</given-names>
          </string-name>
          ,” in
          <source>Management Sciences, Models and Techniques</source>
          ,
          <string-name>
            <surname>C. W. C.</surname>
          </string-name>
          <article-title>a</article-title>
          . o. (eds.), Ed. London: Pergamon,
          <year>1960</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Stockholm</surname>
          </string-name>
          , Sweden: Arbetslivcentrum,
          <year>1988</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>J.</given-names>
            <surname>Greenbaum</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Kyng</surname>
          </string-name>
          , “Design at Work:
          <article-title>Cooperative design of computer systems</article-title>
          ,” . Hillsdale, NJ.: Lawrence Erlbaum,
          <year>1991</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <given-names>W. A.</given-names>
            <surname>Pasmore</surname>
          </string-name>
          , Creating Strategic Change:
          <article-title>Designing the Fliexible, High Performing Organization</article-title>
          . New York: Wiley,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          San Francisco, CA:
          <string-name>
            <surname>Jossey-Bass Inc</surname>
          </string-name>
          ., Publishers,
          <year>1987</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>