<!DOCTYPE html><!--
 * Project   : Research Integrity (RI_INT)
 * Version   : 2.0.0
 * Release   : Thu Apr 13 2023 09:54:27 GMT+0100 (British Summer Time)
 * Copyright : Sage Publications / Epigeum
--><html lang="en" data-programme="Research Integrity" data-course="Export Controls"><head>
		<title>What can go wrong?</title>
		<meta charset="UTF-8">
		<meta http-equiv="X-UA-Compatible" content="IE=edge">
		<meta name="viewport" content="width=device-width, initial-scale=1">

		<link rel="stylesheet" type="text/css" href="../css/project.min.css">
		<link id="basic-print" rel="stylesheet" type="text/css" href="../css/print.min.css" disabled="">
		<link id="summary-print" rel="stylesheet" type="text/css" href="../css/print_interactive.min.css">
		<script type="text/javascript" src="../scripts_scorm_12/SCORM_12_APIWrapper.js"></script>
		<script type="text/javascript" src="../scripts_scorm_12/courseFunctions.js"></script>
	</head>

	<body onload="javascript:Initialize();" onunload="javascript:Terminate();">
	  
		<div id="app" v-cloak="">
			<base-container screen-id="exc_1_50" current-module="Export Controls" page-title="What can go wrong?" screen-time="3" screen-time-period="mins">

				<page-container>

					<page-row>
						<page-content-main>
							
							<p>Export control regulations can be complex. Problems can arise when researchers or research institutions do not understand their responsibilities. Some issues stem from actions taken deliberately, despite the potential consequences; others arise when mistakes are made in understanding and enforcing complex regulations.</p>
							<p>As you read through the following examples, consider what might have been done to avoid these problems.</p>
							
							<instructional-text><p>Click on each of the images for information on various case studies illustrating how things can go wrong when responsible practices are not adhered to when it comes to export controls.</p></instructional-text>
							<accessible-text><p>Continue on for various case studies illustrating how things can go wrong when responsible practices are not adhered to when it comes to export controls.</p></accessible-text>
							
							<!-- ACTIVITY START -->
							<opinions>
								<opinion name="Creating lighter components for aircraft and missiles" img-src="../images/activity_images/course_specific/exc_1_50_img1.png" img-alt="Alt">
									<p>In June 2015, the media highlighted an international consortium, including the University of Birmingham and Imperial College London, who were developing new processes for creating titanium cases for use in aircraft. However, another member of the consortium, a Chinese aerospace manufacturer, had been put on a watchlist by the United States a year earlier for supplying missile technology to Iran. Although it is unclear whether any technologies or processes developed in the UK were utilised by the Iranian missile programme, this case emphasises the possible risks that need to be considered when involved in complex international collaborations (Project Alpha, 2019).</p>
								</opinion>
								<opinion name="Australian researchers concerned by restrictive exports law" img-src="../images/activity_images/course_specific/exc_1_50_img2.png" img-alt="Alt">
									<p>The Australian Defence Trade Controls Act, passed in 2012 (Australian Government, 2012), raised concerns about restrictions on academic freedom. Researchers in cryptology, artificial intelligence and microbiology were reportedly concerned by the restrictions established by this law, which applied to current research projects, and the heavy penalties imposed for violations (Nogrady, 2016).</p>
									<p>Researchers and governments can disagree over what constitutes reasonable controls, which may lead to difficult decisions on the part of researchers, given the risks involved in violating rules (Pearce, 2018).</p>
								</opinion>
								<opinion name="Engaging the wrong students in sensitive research" img-src="../images/activity_images/course_specific/exc_1_50_img3.png" img-alt="Alt">
									<p>Professor Roth, an electrical engineer at the University of Tennessee in the US, invited Chinese and Iranian students to work on Air Force-funded research. He also had information deemed to be sensitive on his computer when he travelled to China to give talks. In 2008, he was accused of violating the US Arms Export Control Act.</p>
									<p>Roth was deeply committed to protecting academic freedom: he felt he had a responsibility to recruit broadly and did not want to turn down students because they came from countries that posed a security risk. He fought the charges but lost, and was sentenced to four years in jail (Golden, 2012).</p>
								</opinion>
								<opinion name="University of Massachusetts: Fined for improper classification of a technology" img-src="../images/activity_images/course_specific/exc_1_50_img4.png" img-alt="Alt">
									<p>In May 2013, the University of Massachusetts at Lowell agreed to pay a fine of $100,000 for illegally exporting an atmospheric testing device to Pakistan. The device was part of a joint research project.</p>
									<p>In this case, the device was ranked at the lowest control level (EAR99) – this meant it would not, generally speaking, be regulated, except in shipments to embargoed or prohibited countries. Had the university sought permission to export the equipment, it might have been granted, but they did not and were, therefore, fined. The fine or penalty, in this case, was levied against the university and not the researchers (Mcvey and Hartwig, 2013).</p>
									<p>The university was put on probation, with the understanding being that the fine would be waived if there were no further violations over the next two years (Burns, 2013).</p>
								</opinion>
							</opinions>
							<!-- ACTIVITY END -->
							
							<p>Consider the following questions, and the problems they present:</p>
							
							<ul>
								<li>If someone in your research group wanted to illegally export restricted information or technology, is there any way you could detect and prevent this?</li>
								<li>How could you protect yourself from the consequences of false charges if you are in regular communication with colleagues in countries that pose security risks?</li>
								<li>What could you do if you felt export control restrictions infringed on the academic freedom needed to move research forward?</li>
								<li>Are there ways to prevent researchers and staff from making wrong assumptions about the export of equipment or information?</li>
								<li>Do export controls restrict academic freedom?</li>
							</ul>
							
							<p>As in other areas of research, the best way to avoid problems is to anticipate and deal with them in advance, or as soon as you identify a potential issue. Questions such as these should be asked in advance of undertaking any work, so that you do not have to deal with the consequences of unwise decisions, lax oversight and situations that could adversely impact your research career.</p>
							
							<h3>Your experience</h3>
							
							<p>Overall, how effective are export control regulations, particularly at your institution?</p>
							
							<instructional-text><p>Indicate whether you agree or disagree with the follow statements. You will be able to see how others taking this module responded once you have submitted your answers.</p></instructional-text>

							<instructional-text-accessible><p>Consider each statement and reflect on your level of agreement or disagreement.</p></instructional-text-accessible>
							
							<!-- ACTIVITY START -->
							<process show-in-accessible-version="false">
								<process-page>
									<!-- POLL START -->
									<poll poll-id="10488796" noscript-text="My institutional offices are knowledgeable about and help researchers understand export regulations."></poll>
									<!-- POLL END -->
								</process-page>
								<process-page>
									<!-- POLL START -->
									<poll poll-id="10488797" noscript-text="Researchers at my institution receive adequate export control training."></poll>
									<!-- POLL END -->
								</process-page>
							</process>
							<!-- ACCESSIBLE START -->
							<accessible-block>
								<h4>Statement 1 of 2:</h4>
								<p>My institutional offices are knowledgeable about and help researchers understand export regulations.</p>
								<h4>Answer options:</h4>
								<ul>
									<li>Strongly agree</li>
									<li>Agree</li>
									<li>Neutral</li>
									<li>Disagree</li>
									<li>Strongly disagree</li>
									<li>Not applicable</li>
								</ul>
								<hr>
								<h4>Statement 2 of 2:</h4>
								<p>Researchers at my institution receive adequate export control training.</p>
								<h4>Answer options:</h4>
								<ul>
									<li>Strongly agree</li>
									<li>Agree</li>
									<li>Neutral</li>
									<li>Disagree</li>
									<li>Strongly disagree</li>
									<li>Not applicable</li>
								</ul>
							</accessible-block>
							<!-- ACCESSIBLE END -->
							<!-- ACTIVITY END -->

							<h3>Summary</h3>
							
							<p>However important you feel export regulations are, or whatever the level of support your institution offers, responsibility (as with so many areas of research) begins with the individual researcher. It is almost certainly the case that the reach and complexity of export controls will grow in our increasingly tense and technical world. This will, in turn, increase the responsibilities that researchers have.</p>
							
						</page-content-main>
					</page-row>
					
				</page-container>
			</base-container>
		</div> <!-- END content wrapper -->
		
		<!-- scripts -->
		<script src="../js/vendor.min.js"></script>
		<script src="../js/vue-components.min.js"></script>
		<script>
			new Vue({
			  el: "#app",
			  data: {},
			  mounted: function () {
				var core = document.createElement('script');
				core.src = "../js/core.min.js";
				document.getElementsByTagName('head')[0].appendChild(core);

				var project = document.createElement('script');
				project.src = "../js/project.min.js";
				document.getElementsByTagName('head')[0].appendChild(project);
			  }
			});
		</script>

	
</body></html>