<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Arial Black";
panose-1:2 11 10 4 2 1 2 2 2 4;}
@font-face
{font-family:"Agency FB";
panose-1:2 11 5 3 2 2 2 2 2 4;}
@font-face
{font-family:"Brush Script Std";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.paragraph, li.paragraph, div.paragraph
{mso-style-name:paragraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.normaltextrun
{mso-style-name:normaltextrun;}
span.eop
{mso-style-name:eop;}
span.spellingerror
{mso-style-name:spellingerror;}
span.contextualspellingandgrammarerror
{mso-style-name:contextualspellingandgrammarerror;}
span.scxw17715981
{mso-style-name:scxw17715981;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">FYI information concerning developments in IT services…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Marquez, Mario A - (marquezm) <marquezm@arizona.edu>
<br>
<b>Sent:</b> Tuesday, November 1, 2022 10:33 AM<br>
<b>To:</b> Galbraith, David W - (galbrait) <galbrait@arizona.edu><br>
<b>Subject:</b> FW: Accelerating Secure IT Services for Campus Units<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is an email that IT directors sent to Barry<o:p></o:p></p>
<p class="MsoNormal">You might want to pass this to the faculty<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i><span style="font-size:14.0pt;font-family:"Brush Script Std";color:#1F497D">Mario A. Marquez<br>
Systems Administrator Principal<br>
University of Arizona<br>
College of Agriculture and Life Sciences<br>
School of Plant Sciences<br>
</span></i></b><b><i><span style="font-size:10.0pt;font-family:"Arial Black",sans-serif;color:#1F497D"><a href="http://www.splshelp.arizona.edu/"><span style="color:blue">http://www.splshelp.arizona.edu/</span></a><br>
<a href="mailto:marquezm@email.arizona.edu">marquezm@email.arizona.edu</a></span></i></b><span style="font-size:14.0pt;font-family:"Brush Script Std";color:#1F497D"><br>
<b><i>Office 520-621-1257<br>
Cell 520-429-2902<o:p></o:p></i></b></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#1F497D"><img border="0" width="198" height="96" style="width:2.0625in;height:1.0in" id="Picture_x0020_3" src="cid:image003.gif@01D8EDDD.3BCAEE60" alt="UAriz-CALS-logo-247"></span><span style="font-size:14.0pt;font-family:"Agency FB",sans-serif;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><br>
<b>Subject:</b> [ditc] Accelerating Secure IT Services for Campus Units<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Dear Barry,</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">As members of Administration Technology Advisory Council (ATAC) and Deans Information Technology Council (DITC), we are committed to improving IT security on the University of
Arizona campus and are asking that UITS collaborate with Unit Level IT moving forward. We are concerned that UITS has been in conversations with the Auditor General about the performance audit review since 2018 but have not involved ATAC or DITC to provide
updates, explain possible solutions, or to collaborate solutions. As discovered by previous university-wide changes, campus units are unique IT ecosystems. Collaborating with campus IT will give
</span><span class="spellingerror">UArizona</span><span class="normaltextrun"> the greatest advantage toward success in addressing the Auditor General’s findings and can help in ensuring an effective approach. We are committed to improving IT security at
</span><span class="spellingerror">UArizona</span><span class="normaltextrun"> and are asking that UITS collaborate with campus IT moving forward.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">The “Accelerating Secure IT Services for Campus Units” plan proposes a nearly complete transfer of service responsibility from campus units to centralized IT. We are concerned
UITS may not have the staffing, understanding of campus IT needs, or communication structure to successfully provide these services at the high level our faculty, staff, and researchers need to meet the UA’s strategic goals. These concerns are validated by
poor ticket response times from UITS, communication problems and issues with previous enterprise level rollouts. From our conversations with UITS during the IT Coordination meetings, a substantial amount of preparatory work by UITS is still necessary before
migration plans can be created by campus IT units, including UITS-provided migration templates, migration guidance, project management definitions of project team members, meeting plans/agendas, defined milestones, and scope definition of Technology Lifecycle
Care (TLC) and Managed Cloud Services (MCS) to delineate those that will be UITS-managed and those that will remain local-IT managed. There also isn’t the communication structure in place, like the one used during the switch to @arizona.edu, that campus IT
requested be used for all UITS projects in the future. Finally, our requests for updates and an evaluation on the takeover of SASG by UITS have gone unanswered. The review of this small-scale consolidation of desktop support under UITS will provide campus
with a better idea of the process and UITS’ ability to provide the support needed. We understand that UITS is understaffed and overstretched so please know that we are here to assist.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">We would like a better understanding of how staff positions are being handled and what options are being made available to employees whose relevance may be reduced or eliminated
by the proposed changes. The abrupt way this plan was announced has had an intense emotional impact on staff across campus. This must be acknowledged. While this project is not directly asking for staff lines from departments, we understand UITS’ budget
needs will grow to support TLC and MCS. Because the UA has finite resources, we understand that much of this funding may be taken from other units on campus. Employees at all levels will appreciate a clear communication of how staff positions will be handled
and what options are being made available to employees whose relevance may be reduced or eliminated by the proposed changes. A compassionate approach would be to reassure our staff that they will be prioritized for positions potentially created within central
IT and to create a plan for transitioning employees so that the UA does not lose highly qualified and trained employees. We also need UITS to clearly define all that is in and out of scope so we can begin making staffing plans for during and after the transition.
We request a better explanation how these changes, possibly resulting in less staff at the local level, will help alleviate the issue of understaffing in local units that was presented as one of the reasons for making this change.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Another major concern for us is that the current TLC and MCS offerings will not be able to address the unique nature of the individual units or the research being done. We agree
that there should not be any exceptions to the need for security, but we do feel that there need to be exceptions to the limited options that UITS has determined that they can support. While these services were being designed, only a small number of campus
IT leadership members were included in the focus groups. The focus group appeared limited to designing the TLC service offering to address the needs of campus units that lacked mature, local IT support rather than being flexible and agile to support campus
units that have requirements for unique or customized services and support. Several members of ATAC and DITC have reached out to UITS to explore using TLC and MCS and found that the services did not support their needs either because of the current service
limitations or the financial costs. The unique IT landscapes are why we hope UITS will be more open and collaborative in their planning moving forward. While UITS is beginning to acknowledge this at the operational level, we need to know that this is being
supported and understood at the highest levels.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Finally, we are concerned over the nature of UITS’ communication methods across campus. This includes tailored communications to different groups, the systematic exclusion of campus
IT leadership from the conversation and the slow rollout of communication channels and templates for projects. TLC and MCS has been the topic of conversation over the last several years but had not been presented as a potential mandatory solution for campus
units until the recent announcement as a finished project. The lack of communication to ATAC and DITC over the last several months, UITS’ unwillingness to track issues and provide minutes for IT Coordination to help improve communication and involvement of
leadership unable to attend all the meetings and the use of significantly different slides/information for campus leadership vs the IT community has fostered mistrust and caution rather than collaboration and the mutual support we need to be successful. Through
collaboration with the leaders and experts affected by this change, we could have answered a number of the questions and concerns and made this process much less anxiety causing for everyone. </span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">We hope that this communication is taken in the constructive manner in which it is intended. We look forward to working with UITS to define a campus It structure that is secure
and still supports the UArizona’s strategic plan, students, faculty, staff, and research at the high level they deserve.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Sincerely,</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Lucas Guthrie, Chair of DITC and Director of IT and Facilities, CAPLA</span><span class="eop"> </span><br>
<span class="normaltextrun">Spink, Beverly, vice-Chair of DITC and Senior Director, Information Technology, UAHS</span><span class="eop"> </span><br>
<span class="normaltextrun">Jeff Kohler, Chair of ATAC and Assistant Athletics Director, IT Operations, Administration and Athletics</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="contextualspellingandgrammarerror">Patrick J.</span><span class="normaltextrun"> Barabe, Director, Information Technology-Computing Support, Graduate College Admin</span><span class="eop"> </span><br>
<span class="normaltextrun">Cynthia Barlow, Information Technology Manager, Principal, Fine Arts Administration</span><span class="eop"> </span><br>
<span class="normaltextrun">Brian Bates, Information Technology Manager, College of Applied Sciences & Technology</span><span class="eop"> </span><br>
<span class="normaltextrun">Ashley D Bidegain, Manager, Information Technology-Systems, James C Wyant College of Optical Sciences</span><span class="eop"> </span><br>
<span class="normaltextrun">Drennen A Brown, Director, Information Technologies and Spatial Services, Planning Design & Construction</span><span class="eop"> </span><br>
<span class="normaltextrun">Christina A Carbone, Information Technology Manager, Mathematics</span><span class="eop"> </span><br>
<span class="normaltextrun">Steven J </span><span class="contextualspellingandgrammarerror">Chang, Department</span><span class="normaltextrun"> Head, Technology Strategy and Services, Technology Strategy & Services</span><span class="eop"> </span><br>
<span class="normaltextrun">Leo J Enfield, Information Technology Manager, Principal, Engineering Administration</span><span class="eop"> </span><br>
<span class="normaltextrun">Robert D Flores, IT Support Helpdesk Analyst III, Arizona State Museum</span><span class="eop"> </span><br>
<span class="normaltextrun">Jose Fragoso, Assistant Director, Technology Services, Housing & Residential Life</span><span class="eop"> </span><br>
<span class="normaltextrun">David Gay, Director, Information Technology-Computing Support, Public Health Administration</span><span class="eop"> </span><br>
<span class="normaltextrun">Rey Granillo, Manager, Development and Information Technology, AZ Institute for Resilience</span><span class="scxw17715981"> </span><br>
<span class="normaltextrun">Michael Griffith, Director, Digital Initiatives, College of Education</span><span class="eop"> </span><br>
<span class="normaltextrun">Jason L Katterhenry, Director, Information Technology Services - AZPM</span><span class="eop"> </span><br>
<span class="normaltextrun">Shawn </span><span class="spellingerror">Kolofer</span><span class="normaltextrun">, Lead Specialist, Infrastructure, Eller Information Technology</span><span class="eop"> </span><br>
<span class="normaltextrun">Steve Machtley, Assistant Dean, Learning - Healthcare Technology Innovations, College of Nursing</span><span class="eop"> </span><br>
<span class="normaltextrun">Dan C Mayhew, Director, Information Technology, Information Technology</span><span class="eop"> </span><br>
<span class="normaltextrun">David Mayhew, Manager, Operations, Technology Strategy & Services</span><span class="eop"> </span><br>
<span class="normaltextrun">Lizeth Mora, Senior Director, Information Technology, Social & Behavioral Sciences</span><span class="eop"> </span><br>
<span class="normaltextrun">Elia Nazarenko, Lead, Platforms, Technology Strategy & Services</span><span class="eop"> </span><br>
<span class="normaltextrun">Bryant Parker, Director, Eller IT, Eller Information Technology</span><span class="eop"> </span><br>
<span class="normaltextrun">Rahr, Matt, Director, Cyber & Information Technologies, CALS</span><span class="eop"> </span><br>
<span class="normaltextrun">Collin Rogow, Principal IT Architect, Veterinarian Medicine Administration</span><span class="eop"> </span><br>
<span class="normaltextrun">Bart Rossmann, Director, Instructional and Research Computing, Humanities Administration</span><span class="eop"> </span><br>
<span class="normaltextrun">Robert J Sommerfeld, Assistant Chief, University of Arizona Police Department</span><span class="eop"> </span><br>
<span class="normaltextrun">Tony Schlak, Director, Information Technology, Pharmacy Administration</span><span class="eop"> </span><br>
<span class="normaltextrun">Michael S Wagenheim, Assistant Dean, Information Technology and Online Learning, College of Law</span><span class="eop"> </span><br>
<span class="normaltextrun">Kevin D Williams, Director, Facilities Management Information Technology, Facilities Management</span><span class="eop"> </span><br>
<span class="normaltextrun">Ed Xia, Assistant Dean, College of Medicine Information Technology Services, COM Info Technology Services</span><span class="eop"> </span><br>
<span class="normaltextrun">Travis S Zwickl, Systems Administrator, Principal, Arizona Global</span><span class="eop"> </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><img border="0" width="120" height="96" style="width:1.25in;height:1.0in" id="Picture_x0020_1" src="cid:image001.png@01D8E7CD.1F330960" alt="The University of Arizona block 'A' logo."><o:p></o:p></p>
</td>
<td width="500" valign="top" style="width:375.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:14.0pt;color:#0C234B">Lucas M Guthrie</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#495057">Director of Information Technology and Facilities<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#495057">College of Architecture, Planning and Landscape Architecture<br>
ARCHITECTURE, 203<br>
PO BOX 210075 | TUCSON, AZ 85721-0075<br>
Office: 520-621-0448 </span><span style="font-size:9.0pt;color:#767676">| </span>
<span style="font-size:10.0pt;color:#495057">Cell: 555-555-5555 <br>
<a href="mailto:lucasg@arizona.edu"><span style="color:#495057">lucasg@arizona.edu</span></a><br>
<a href="https://arizona.zoom.us/j/606908881"><span style="color:blue">https://arizona.zoom.us/j/606908881</span></a><br>
<b><a href="https://capla.arizona.edu/"><span style="color:#8B0015">capla.arizona.edu</span></a></b><br>
</span><span style="font-size:9.0pt;color:#767676">| </span><span style="font-size:10.0pt;color:#495057"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width="120" style="width:1.25in;padding:0in 0in 0in 0in"></td>
<td width="500" style="width:375.0pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><a href="https://brand.arizona.edu/signature"><span style="color:blue;text-decoration:none"><img border="0" width="400" height="96" style="width:4.1666in;height:1.0in" id="Picture_x0020_2" src="cid:image002.png@01D8E7CD.1F330960" alt="Integrity, Compassion, Exploration, Adaptation, Inclusion, Determination"></span></a><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>