<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Teaming.AI: Enabling Human-AI Teaming Intelligence in Manufacturing</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Thomas</forename><surname>Hoch</surname></persName>
							<email>thomas.hoch@scch.at</email>
							<affiliation key="aff0">
								<orgName type="department">Software Competence Center Hagenberg</orgName>
								<address>
									<addrLine>Softwarepark 32a</addrLine>
									<postCode>4232</postCode>
									<settlement>Hagenberg</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Bernhard</forename><surname>Heinzl</surname></persName>
							<email>bernhard.heinzl@scch.at</email>
							<affiliation key="aff0">
								<orgName type="department">Software Competence Center Hagenberg</orgName>
								<address>
									<addrLine>Softwarepark 32a</addrLine>
									<postCode>4232</postCode>
									<settlement>Hagenberg</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Gerald</forename><surname>Czech</surname></persName>
							<email>gerald.czech@ooelfv.at</email>
							<affiliation key="aff1">
								<orgName type="institution">Upper Austrian Fire Brigade Association</orgName>
								<address>
									<addrLine>Hauptstraße 1-5</addrLine>
									<postCode>4041</postCode>
									<settlement>Linz</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Maqbool</forename><surname>Khan</surname></persName>
							<email>maqbool.khan@scch.at</email>
							<affiliation key="aff0">
								<orgName type="department">Software Competence Center Hagenberg</orgName>
								<address>
									<addrLine>Softwarepark 32a</addrLine>
									<postCode>4232</postCode>
									<settlement>Hagenberg</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="department" key="dep1">Sino-Pak Center for Artificial Intelligence</orgName>
								<orgName type="department" key="dep2">PAF-IAST</orgName>
								<address>
									<settlement>Khanpur Road</settlement>
									<country key="PK">Pakistan</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Philipp</forename><surname>Waibel</surname></persName>
							<email>philipp.waibel@wu.ac.at</email>
							<affiliation key="aff3">
								<orgName type="institution">Vienna University of Economics and Business</orgName>
								<address>
									<addrLine>Welthandelspl. 1</addrLine>
									<postCode>1020</postCode>
									<settlement>Vienna</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Stefan</forename><surname>Bachhofner</surname></persName>
							<email>stefan.bachhofner@wu.ac.at</email>
							<affiliation key="aff3">
								<orgName type="institution">Vienna University of Economics and Business</orgName>
								<address>
									<addrLine>Welthandelspl. 1</addrLine>
									<postCode>1020</postCode>
									<settlement>Vienna</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Elmar</forename><surname>Kiesling</surname></persName>
							<email>elmar.kiesling@wu.ac.at</email>
							<affiliation key="aff3">
								<orgName type="institution">Vienna University of Economics and Business</orgName>
								<address>
									<addrLine>Welthandelspl. 1</addrLine>
									<postCode>1020</postCode>
									<settlement>Vienna</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Bernhard</forename><surname>Moser</surname></persName>
							<email>bernhard.moser@scch.at</email>
							<affiliation key="aff0">
								<orgName type="department">Software Competence Center Hagenberg</orgName>
								<address>
									<addrLine>Softwarepark 32a</addrLine>
									<postCode>4232</postCode>
									<settlement>Hagenberg</settlement>
									<country key="AT">Austria</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Teaming.AI: Enabling Human-AI Teaming Intelligence in Manufacturing</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">1CBB21EFED1D87C66C7674947EE184C6</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T07:21+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Fault detection and diagnosis, decision-making and cognitive processes, human-centred automation, knowledge modeling, knowledge based systems 0000-0003-0074-0052 (T. Hoch)</term>
					<term>0000-0001-8297-7533 (B. Heinzl)</term>
					<term>0000-0001-7656-0184 (M. Khan)</term>
					<term>0000-0002-5562-4430 (P. Waibel)</term>
					<term>0000-0001-7785-2090 (S. Bachhofner)</term>
					<term>0000-0002-7856-2113 (E. Kiesling)</term>
					<term>0000-0001-8373-7523 (B. Moser)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Teaming.AI aims to overcome the lack of flexibility as a limiting factor of human-centered AI collaboration by envisioning a teaming framework that integrates the strengths of both, namely the flexibility of human intelligence and the scaling and processing capabilities of machine intelligence. In Teaming.AI, this will be achieved by employing a teaming model that structures the interactions between humans and AI systems, and a knowledge graph that dynamically supports the teaming model to cope with process, regulatory and context knowledge. We expect that the developed Teaming.AI platform provides the human team members with a better understanding and control of automated services and decision support within the manufacturing environment, leading to a more trustful collaboration between the human and AI.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>The Teaming.AI project aims to address the open problem of the "missing middle" (see <ref type="bibr" target="#b0">[1]</ref>) in scenarios where humans and AI systems collaborate towards a common goal. This missing middle is defined along a spectrum between human-only to machine-only activities. Human only activities include leading, empathizing, creating, and judging; machine-only activities include transacting, iterating, predicting and adapting. The "missing middle" lies in between these extremes -i.e., human and machine hybrid activities. These can be broken down into teaming activities where (i) "humans complement machines" (i.e., train, explain, sustain) and (ii) "AI gives humans superpowers" (amplify, interact, embody). Such hybrid activities are neglected in the state of the art and deserve more recognition, especially given the observation that human intelligence outperforms current AI systems in a wide field of applications, particularly in terms of flexibility and taking context into account.</p><p>The envisioned Teaming.AI approach aims to support the systematic development and evolution of AI systems in manufacturing in order to address current limitations of today's narrow AI systems. Such systems typically lack self-adaptive capabilities and the ability to assimilate and interpret new information outside of its predefined programmed parameters. They are typically tailored to solve specific tasks in a specific predefined setting; changes in this underlying setting typically requires system adaptations, ranging from fine-grained parameter adaptations to fully-fledged re-design and re-development of AI systems. In order to tackle this challenge, Teaming.AI has to provide a flexible framework to specify mechanisms for collaborative self-adaptation of the overall system that may involve both human actors and AI agents. Employing a teaming model provides a flexible way for performing adaptations on multiple levels, taking inspiration from conceptual models of self-adaptive systems developed in the software engineering literature (cf. <ref type="bibr" target="#b1">[2]</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related work</head><p>The teaming intelligence of humans has been studied and practiced several decades ago in the research community to increase the productivity and lessen task completion duration. The advancement in robot technologies pushed the teaming concept to a new era of human collaboration with machines, agents and AI systems. Within recent years, the advancement in technology has created robots and AI systems being able to perform a variety of tasks in manufacturing, space, agriculture, healthcare, autonomous vehicles and in other real-life scenarios <ref type="bibr" target="#b2">[3]</ref>. Human-robot teaming is studied from multiple perspectives, such as: concepts and design components <ref type="bibr" target="#b3">[4]</ref>, perspective on analysis and implementation issues <ref type="bibr" target="#b4">[5]</ref>, human-robot interaction theory <ref type="bibr" target="#b5">[6]</ref>, Humanrobot cross-training <ref type="bibr" target="#b6">[7]</ref>, and mutual trust between human and robot in decision making <ref type="bibr" target="#b7">[8]</ref>.</p><p>[9] studied human teamwork and identified five core components for effective teaming (see Figure <ref type="figure" target="#fig_0">1A</ref>), considering not only whether the team performed well (e.g., completed the team task) but also how the team interacted (i.e., team processes, teamwork) to achieve the team outcome. They argued, that team effectiveness can be improved by a well-designed coordination mechanisms to ensure that the "Big Five" are consistently updated and that relevant information is distributed throughout the team. Recently, research has made advancements towards achieving common goals by human and autonomous systems using their unique capabilities for specific portions of a task as a team. The current collaborative teaming concepts like human-agent teaming <ref type="bibr" target="#b9">[10]</ref> and human-autonomy teaming <ref type="bibr" target="#b10">[11]</ref> are the motivation of our proposed Teaming.AI platform towards a novel approach for human-AI teaming.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">High-level perspective on teaming</head><p>Although the study of <ref type="bibr" target="#b8">[9]</ref> focuses purely on human teaming and not human-AI teaming, we believe this theory builds a solid foundation for the digitalization of human-AI teaming interaction for two reasons. First, the clear segregation of teamwork and coordination mechanisms supports separation of concerns in digitalization. Second, we believe that team effectiveness as a goal instead of team performance keeps human team members more in the focus than AI, because team performance only incorporates the outcome of the work, while team effectiveness also takes the interactions among team members into account. To be an effective team member, the AI must take part in the coordination activities of the team, and it needs to know what information to share or when to ask for assistance. Being capable of observing one another's state, sharing information, or requesting assistance is regarded by <ref type="bibr" target="#b11">[12]</ref> as Teaming Intelligence. <ref type="bibr" target="#b12">[13]</ref> captured human-AI teaming requirements beyond traditional task-based approaches towards human-autonomy teaming (i.e. human-AI teaming preserving human autonomy). We believe that this fits well to achieve team effectiveness as defined by <ref type="bibr" target="#b8">[9]</ref>. Human autonomy teaming requires understanding interdependency. <ref type="bibr" target="#b12">[13]</ref> defines an Interdependence Analysis tool to understand how people and automation can effectively team by providing insight into the interdependence relationships used to support one another throughout an activity.</p><p>In Teaming.AI, we follow these design principles and analyze the interdependence relationships along the four dimensions of the 4S framework as described by <ref type="bibr" target="#b11">[12]</ref>. Starting from the analysis of team and task structure, the skills of the team actors are identified and linked to the different teaming activities. Different to <ref type="bibr" target="#b12">[13]</ref> and their concept of jointness, we expect that, at the most granular level, an activity is either performed by a human team member or an automated AI service. However, the performer of this activity can be supported either by a human or the AI by providing additional insights the performer can rely on. We introduce abstract activities as a mechanism to model this performer/supporter pattern. We envision the supporter role as a more passive role that monitors the current state of the production process and interacts if needed, similar as described by <ref type="bibr" target="#b13">[14]</ref>. <ref type="bibr" target="#b11">[12]</ref> defined Teaming Intelligence as intelligently managing the interdependencies of coordination work. Teaming.AI offers a method to manage these interdependencies and interactions by modelling them in a structured manner and linking these models to relevant activities, resources, and constraints (policies). To this end, the teaming model is comprised of multiple sub-models, in particular:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Teaming model</head><p>Teaming Process Model: The teaming process model defines the individual teaming processes and tasks, describing the state, structure, skills, and strategy of teaming interaction between human and the Teaming.AI platform according to the 4S framework. The teaming process model is instantiated and executed by the teaming engine within the Teaming.AI platform.</p><p>Activity Model: To achieve a high interchangeability, the information that is required for the concrete/abstract activities is separated from the teaming process model. The activity model is responsible for storing and querying the activity information. The activity model enriches the activities in the teaming process model with additional information required to execute the processes, such as necessary inputs, preconditions, and generated outputs.</p><p>Event Model: The teaming model is used by the teaming engine (see Figure <ref type="figure" target="#fig_0">1B</ref>) to orchestrate the teaming aspects of the process execution and to act in case specific events are detected. If an event is detected, the teaming engine uses the teaming process model to decide on the next tasks that must be performed, together with the information who is performing the task, by considering policies and other aspects (e.g., human skills or organizational roles). </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Policy Model:</head><p>The policy model enriches the overall teaming model with additional information regarding rules that control the teaming process in order to achieve effective teaming interaction and fulfill the team's goals. In particular, this encompasses external policies adhering to legal and ethical requirements or company regulations, as well as internal policies that are rules driven by the teaming process and provide a mechanism to increase flexibility and make the teaming process more adaptive at runtime. These teaming model elements are formalized and stored in a knowledge graph, which makes it possible to associate and ground them in application-specific background knowledge -i.e., a concrete description of organizational roles and responsibilities, the production system, its resources and its environment, as well as industrial products and production processes. The teaming model should provide means to model effective teaming interaction according to the "Big Five" framework as well as enabling coordinating mechanisms that form a trust-enhancing communication cycle.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Teaming.AI platform overview</head><p>The Teaming.AI platform supports the development and execution of a flexible model for dynamic teaming of human stakeholders and AI systems in order to improve learning and knowledge transfer. A key goal is to enable better coordination of work sharing across teams of human agents and AI components. The central coordination element in the Teaming.AI platform is the Teaming Engine, which monitors the execution environment, tracks the dynamic context of the enacted teaming process in the production environment and applies policies to orchestrate teaming processes. This includes making decisions based on specified policies, e.g., who executes a specific task, when roles between task performer and task supporter need to be switched etc.</p><p>Figure <ref type="figure" target="#fig_0">1B</ref> depicts the architectural components of the Teaming.AI platform. The interaction and communication are based on events, which are handled by a central event stream broker. Events can be enriched either automatically or manually with specific process knowledge (e.g., machine data or error descriptions). The knowledge graph runtime is responsible for filtering and aggregating these events into meaningful so-called complex events. These complex events are stored in a dynamic data knowledge graph and analyzed further in order to identify higher level correlations that can be used for decision making (e.g., to automate quality inspection of work pieces). With the use of a knowledge graph <ref type="bibr" target="#b14">[15]</ref>, we strive for solutions that allow for the generation of ML models that are easier to interpret and can make the derived information semantically explicit.</p><p>The knowledge in Teaming.AI has both static and dynamic parts. As static knowledge, we consider all knowledge that only changes at low frequencies (e.g., less than daily), for example product data, organizational structures, and policies. Dynamic knowledge on the other hand changes at higher frequencies, which may include data streams (e.g., state of machines or work pieces). These updates are retrieved from the event stream broker and need to be incorporated into the knowledge graph, e.g., by means of stream reasoning (see <ref type="bibr" target="#b15">[16]</ref>) or online machine learning (see <ref type="bibr" target="#b16">[17]</ref>).</p><p>Most current knowledge graph solutions have comparatively low update rates and would be considered static in the above frequency-of-change based definition. Hence, novel techniques are required that refine the current state of the art in knowledge graph processing. In Teaming.AI, we follow a modular approach that facilitates purpose-driven, agile construction of reusable knowledge graphs across multiple layers of abstraction and perspectives. This means e.g., that every layer of the knowledge graph represents a partial view on the real-world system that links relevant aspects for a given perspective (e.g. business / operational).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusion</head><p>A key element for successful human-AI teamwork is a careful design and implementation of the coordinating mechanisms involved. Mutual trust increases if the appropriate amount of information is shared through a closed-loop communication between humans and AI components. The envisioned Teaming.AI platform has the goal to orchestrate the information exchange and to organize the collected information within a layered knowledge graph, reduce the information to its key aspects and semantically enrich this knowledge with context information. Transparent storage and processing of information is the foundation for a decision support system that can be understood and further analyzed by human team members.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: The Big Five of teamwork and their coordinating mechanisms (left). Overview of the Teaming.AI architecture (right).</figDesc><graphic coords="3,86.20,382.72,416.61,189.95" type="bitmap" /></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Acknowledgements</head><p>The project Teaming.AI has received funding from the European Union's Horizon 2020 research and innovation program under grant agreement No. 957402.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Human + machine: Reimagining work in the age of AI</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">R</forename><surname>Daugherty</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">J</forename><surname>Wilson</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2018">2018</date>
			<publisher>Harvard Business Press</publisher>
			<pubPlace>Harvard</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Software engineering of self-adaptive systems: an organised tour and future challenges</title>
		<author>
			<persName><forename type="first">D</forename><surname>Weyns</surname></persName>
		</author>
		<ptr target="https://people.cs.kuleuven.be/~danny.weyns/papers/2017HSE.pdf" />
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Human-robot collaboration: A survey</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bauer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Wollherr</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Buss</surname></persName>
		</author>
		<idno type="DOI">10.1142/S0219843608001303</idno>
	</analytic>
	<monogr>
		<title level="j">International Journal of Humanoid Robotics</title>
		<imprint>
			<biblScope unit="volume">05</biblScope>
			<biblScope unit="page" from="47" to="66" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">M</forename><surname>Ma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Fong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Micire</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">M</forename><surname>Feigh</surname></persName>
		</author>
		<ptr target="http://www.fsr.ethz.ch/papers/FSR_2017_paper_57.pdf" />
		<title level="m">Human-robot teaming: Concepts and components for design</title>
				<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Human-robot teaming: Perspective on analysis and implementation issues</title>
		<author>
			<persName><forename type="first">A</forename><surname>Chella</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Lanza</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Pipitone</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Seidita</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-2352/short3.pdf" />
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<editor>
			<persName><forename type="first">A</forename><surname>Finzi</surname></persName>
		</editor>
		<editor>
			<persName><surname>Farinelli</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">F</forename><surname>Anzalone</surname></persName>
		</editor>
		<editor>
			<persName><surname>Mastrogiovanni</surname></persName>
		</editor>
		<imprint>
			<biblScope unit="volume">2352</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Human-agent and human-robot interaction theory: Similarities to and differences from human-human interaction</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">C</forename><surname>Krämer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">M R</forename><surname>Der Pütten</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">C</forename><surname>Eimler</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-642-25691-2_9</idno>
	</analytic>
	<monogr>
		<title level="m">Human-Computer Interaction: The Agency Perspective</title>
				<editor>
			<persName><forename type="first">M</forename><surname>Zacarias</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Valente De Oliveira</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="215" to="240" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Human-robot cross-training: Computational formulation, modeling and evaluation of a human team training strategy</title>
		<author>
			<persName><forename type="first">S</forename><surname>Nikolaidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A</forename><surname>Shah</surname></persName>
		</author>
		<idno type="DOI">10.1109/HRI.2013.6483499</idno>
	</analytic>
	<monogr>
		<title level="m">8th ACM/IEEE International Conference on Human-Robot Interaction (HRI)</title>
				<meeting><address><addrLine>New York</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2013">2013</date>
			<biblScope unit="page" from="33" to="40" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Planning with trust for human-robot collaboration</title>
		<author>
			<persName><forename type="first">M</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Nikolaidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Soh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Hsu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Srinivasa</surname></persName>
		</author>
		<idno type="DOI">10.1145/3171221.3171264</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2018 ACM/IEEE International Conference on Human Robot Interaction</title>
				<meeting>the 2018 ACM/IEEE International Conference on Human Robot Interaction<address><addrLine>New York</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="307" to="315" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Is there a &quot;big five&quot; in teamwork?</title>
		<author>
			<persName><forename type="first">E</forename><surname>Salas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">E</forename><surname>Sims</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">S</forename><surname>Burke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Small group research</title>
		<imprint>
			<biblScope unit="volume">36</biblScope>
			<biblScope unit="page" from="555" to="599" />
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Human-agent teaming for multirobot control: A review of human factors issues</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">Y C</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>Barnes</surname></persName>
		</author>
		<idno type="DOI">10.1109/THMS.2013.2293535</idno>
	</analytic>
	<monogr>
		<title level="j">IEEE Transactions on Human-Machine Systems</title>
		<imprint>
			<biblScope unit="volume">44</biblScope>
			<biblScope unit="page" from="13" to="29" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Team interaction strategies for human-autonomy teaming in next generation combat vehicles</title>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">J</forename><surname>Lematta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">J</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Holder</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Huang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Bhatti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">J</forename><surname>Cooke</surname></persName>
		</author>
		<idno type="DOI">10.1177/1071181320641022</idno>
	</analytic>
	<monogr>
		<title level="j">Proceedings of the Human Factors and Ergonomics Society Annual Meeting</title>
		<imprint>
			<biblScope unit="volume">64</biblScope>
			<biblScope unit="page" from="77" to="81" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">No AI is an island: the case for teaming intelligence</title>
		<author>
			<persName><forename type="first">M</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Vera</surname></persName>
		</author>
		<idno type="DOI">10.1609/aimag.v40i1.2842</idno>
	</analytic>
	<monogr>
		<title level="j">AI Magazine</title>
		<imprint>
			<biblScope unit="volume">40</biblScope>
			<biblScope unit="page" from="16" to="28" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">Understanding human-machine teaming through interdependence analysis</title>
		<author>
			<persName><forename type="first">M</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Vignatti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Duran</surname></persName>
		</author>
		<editor>M. D. McNeese, E. Salas, M. R. Endsley</editor>
		<imprint>
			<date type="published" when="2020">2020</date>
			<publisher>CRC Press</publisher>
			<biblScope unit="page" from="209" to="233" />
			<pubPlace>Boca Raton</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Human modeling and interaction in cyber-physical systems: A reference framework</title>
		<author>
			<persName><forename type="first">D</forename><surname>Şahinel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Akpolat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><forename type="middle">C</forename><surname>Görür</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Sivrikaya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Albayrak</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.jmsy.2021.03.002</idno>
	</analytic>
	<monogr>
		<title level="j">Journal of Manufacturing Systems</title>
		<imprint>
			<biblScope unit="volume">59</biblScope>
			<biblScope unit="page" from="367" to="385" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Knowledge graphs</title>
		<author>
			<persName><forename type="first">A</forename><surname>Hogan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Blomqvist</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cochez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>D'amato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>De Melo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Gutierrez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kirrane</surname></persName>
		</author>
		<author>
			<persName><forename type="first">…</forename><forename type="middle">A</forename><surname>Zimmermann</surname></persName>
		</author>
		<idno type="DOI">10.1145/3447772</idno>
	</analytic>
	<monogr>
		<title level="j">ACM Computing Surveys</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="page" from="1" to="37" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Stream reasoning: A survey and outlook</title>
		<author>
			<persName><forename type="first">D</forename><surname>Dell'aglio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">Della</forename><surname>Valle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Van Harmelen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Bernstein</surname></persName>
		</author>
		<idno type="DOI">10.3233/DS-170006</idno>
	</analytic>
	<monogr>
		<title level="j">Data Science</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="59" to="83" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Online learning: A comprehensive survey</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">C</forename><surname>Hoi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sahoo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Zhao</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.neucom.2021.04.112</idno>
	</analytic>
	<monogr>
		<title level="j">Neurocomputing</title>
		<imprint>
			<biblScope unit="volume">459</biblScope>
			<biblScope unit="page" from="249" to="289" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
