<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)">
<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:"Microsoft Sans Serif";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.cs2654ae3a, li.cs2654ae3a, div.cs2654ae3a
{mso-style-name:cs2654ae3a;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.cs1e88c66e, li.cs1e88c66e, div.cs1e88c66e
{mso-style-name:cs1e88c66e;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial",sans-serif;
color:black;}
p.cs157f42b2, li.cs157f42b2, div.cs157f42b2
{mso-style-name:cs157f42b2;
margin-top:22.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.csadfa96c3, li.csadfa96c3, div.csadfa96c3
{mso-style-name:csadfa96c3;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial",sans-serif;
color:#0563C1;
text-decoration:underline;}
p.cs1ba52a26, li.cs1ba52a26, div.cs1ba52a26
{mso-style-name:cs1ba52a26;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial",sans-serif;
color:black;
font-weight:bold;}
p.cs2f1b7012, li.cs2f1b7012, div.cs2f1b7012
{mso-style-name:cs2f1b7012;
margin-top:8.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.csd9ae63c1, li.csd9ae63c1, div.csd9ae63c1
{mso-style-name:csd9ae63c1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Arial",sans-serif;
color:black;
text-decoration:underline;}
p.cs557ef5b0, li.cs557ef5b0, div.cs557ef5b0
{mso-style-name:cs557ef5b0;
margin-top:8.0pt;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.csedbfcf26, li.csedbfcf26, div.csedbfcf26
{mso-style-name:csedbfcf26;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Microsoft Sans Serif",sans-serif;
color:black;}
span.cs1e88c66e1
{mso-style-name:cs1e88c66e1;
font-family:"Arial",sans-serif;
color:black;
font-weight:normal;
font-style:normal;}
span.csadfa96c31
{mso-style-name:csadfa96c31;
font-family:"Arial",sans-serif;
color:#0563C1;
font-weight:normal;
font-style:normal;
text-decoration:underline;}
span.cs1ba52a261
{mso-style-name:cs1ba52a261;
font-family:"Arial",sans-serif;
color:black;
font-weight:bold;
font-style:normal;}
span.csd9ae63c11
{mso-style-name:csd9ae63c11;
font-family:"Arial",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:underline;}
span.csedbfcf261
{mso-style-name:csedbfcf261;
font-family:"Microsoft Sans Serif",sans-serif;
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle32
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1685588330;
mso-list-type:hybrid;
mso-list-template-ids:558294264 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hello MVECA Treasurers!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Here’s an addendum to the email you received regarding the Redesign.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MVECA will not bill our districts for the $.50/ADM charge, at this time.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If you did not submit a wave request form, please complete the attached form and forward it to me by the end of this week. The waves are in 6 month
periods. It doesn’t take 6 months to migrate your data. We will start testing and training 2 months before your requested go live date. Please consider the best time for parallel processing when requesting a wave. You will need to parallel at least 2 payrolls
and one month in USAS. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Let us know if you have any questions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Deb, Ashley and Marsha<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Ohio-K12 DoNotReply <donotreply@ohio-k12.help>
<br>
<b>Sent:</b> Tuesday, July 23, 2019 10:50 AM<br>
<b>To:</b> Debra Dinnen <dinnen@mveca.org><br>
<b>Subject:</b> Project Message #14: Update on USAS Redesign - July, 2019<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="cs2654ae3a"><span class="cs1e88c66e1"><span style="font-size:10.0pt">To: District Treasurers currently using USAS/USPS or Redesign, ITC USAS/USPS Fiscal Support Staff, ITC Directors</span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Date: July 23, 2019</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1e88c66e1"><span style="font-size:10.0pt">This Redesign Project update focuses on key questions about recent changes to State Software and the State Software Development Team. To keep those interested in the progress of
Redesign adoptions informed, attached please find an updated map showing names and approximate locations of those now using Redesign in production, or intending to migrate in the current wave (July – Dec. 2019). Questions about this update may be directed
to </span></span><span class="csadfa96c31"><span style="font-size:10.0pt"><a href="mailto:fiscal.redesign@ohio-k12.org">fiscal.redesign@ohio-k12.org</a></span></span><span class="cs1e88c66e1"><span style="font-size:10.0pt">.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">Why must the Classic software be retired?</span></span><o:p></o:p></p>
<p class="cs2f1b7012"><span class="cs1e88c66e1"><span style="font-size:10.0pt">There have been many opinions, concerns and candidly, frustration from districts regarding the retirement of Classic state software. The State Software Development Team (SSDT) very
much understands your concerns and frustrations and we, along with the State Software Advisory Committee and the Management Council of the Ohio Education Computer Network (MCOECN), felt that a special communication addressing your questions would help everyone
better understand why the software needed to be redesigned and why the Classic software has a 'sunset' date. We hope after reading this edition you come away with a better understanding of the migration effort and the future of state software.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">Why retire Classic?</span></span><o:p></o:p></p>
<p class="cs2f1b7012"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Classic State Software is dependent on an operating system and associated applications and hardware that are obsolete and being retired by the companies that created and supported
them for decades. Though a possible upgrade path for an untested iteration of the operating system exists through a different company, the replacement system would cost nearly five times more, it would not address hardware issues, and such a move would place
additional burdens on technical staff supporting Classic across the state. From multiple perspectives—financial, support and functional—it is in our collective interest to move to the modern Redesign solution as quickly as possible.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">When will Classic retire?</span></span><o:p></o:p></p>
<p class="cs2f1b7012"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Recognizing the financial and labor costs of maintaining Classic State Software as well as the time it will take to move hundreds of districts to a modern infrastructure, the timeline
SSDT is pursuing and planning around has Classic retiring at the </span></span><span class="csd9ae63c11"><span style="font-size:10.0pt">end of December 2022</span></span><span class="cs1e88c66e1"><span style="font-size:10.0pt">. After that date, no updates
to the software are anticipated, including all tax forms and tables. Of course, W2s and 1099s for 2022 will be available in early 2023. Additionally, we are developing a capability for accessing archived data for historical purposes after 2022.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">There is a new support fee for State Software for districts. Why is it needed, how much will it cost and when will it be assessed?</span></span><o:p></o:p></p>
<p class="cs2f1b7012"><span class="cs1e88c66e1"><span style="font-size:10.0pt">On July 1, the Management Council of the Ohio Education Computer Network assumed fiscal responsibility for the State Software effort. In order to migrate all districts that wish
to move to the Redesign prior to the December 2022 sunset date cited above, funds are needed to maintain Classic through the transitionary period, as well as to expedite Redesign development. This will enable the Management Council to hire more programmers
and support staff at the SSDT, which will in turn assist schools and ITCs in their migrations to Redesign. Also, due to the additional complexity and sophistication of the technical tools being used for the Redesign, there is a need for a scalable technical
environment that requires investment in hardware and consulting. To meet this array of needs, </span></span><span class="csd9ae63c11"><span style="font-size:10.0pt">ITCs will be collecting a support fee of $.50 per ADM for districts using State Software,
regardless if they are using Classic or Redesign</span></span><span class="cs1e88c66e1"><span style="font-size:10.0pt">, beginning in FY 2020. The funds generated are necessary to sustain current development momentum, continue district migrations </span></span><span class="csd9ae63c11"><span style="font-size:10.0pt">and</span></span><span class="cs1e88c66e1"><span style="font-size:10.0pt"> help
build and support a much more robust and modern financial application that will serve Ohio schools for many years. </span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">What are the timelines for A/R (Accounts Receivable) and Inventory?</span></span><o:p></o:p></p>
<p class="cs2f1b7012"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Within Redesign, the accounting and payroll functions are in place and the software has the necessary reports to assist districts with their daily processing. The Accounts Receivable
module, Inventory module, and various workflow functions are in early stages of planning and development. Accounts Receivable is projected to be live in summer of 2020. In the interim, districts can continue to use the Accounts Receivable module in Classic
State Software, importing results into Redesign’s accounting system via pending transactions. User also have the option to post summary receipts. Inventory is projected to be live in summer of 2021. In the interim, districts can continue using EIS for their
inventory. SSDT has an inventory extract in Redesign that will extract data which can then be imported into the pending file in Classic EIS. While these module developments are still in the future, it is appropriate to note that 63 Ohio school districts
are already running their fiscal operations live on Redesign and another 54 are scheduled to migrate in the second half of 2019.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">Has a statewide wave migration schedule been established?</span></span><o:p></o:p></p>
<p class="cs557ef5b0"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Work has begun on establishing a Statewide migration schedule in six month "waves," in coordination with all ITCs. Waves start every six months, beginning each January and July.
Information Technology Center (ITC) fiscal staff are working with the districts they serve to determine when each district will be able to migrate. If your ITC has not been in touch with your district regarding wave placement, please contact your ITC for
further information.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">How will input from the field be gathered and used to inform Redesign?</span></span><o:p></o:p></p>
<p class="cs557ef5b0"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Recently, the Fiscal Redesign Oversight Committee (FROC)—established in 2015—met for the last time after helping the project get to a point where there are now over 60 districts
successfully using the product for accounting and payroll purposes. FROC co-chairs Ed Weisenbach from ODE and Geoff Andrews from the Management Council expressed sincere appreciation to FROC members for completing their oversight responsibilities.
</span></span><o:p></o:p></p>
<p class="cs557ef5b0"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Acknowledging the need for continuous feedback from the field as the Redesign matures, FROC members heard updates on the State Software Advisory Committee that was reconstituted
in October 2018. Agreeing to meet quarterly to help the SSDT guide and direct the development of State Software, bylaws adopted by the State Software Advisory Committee call for ITC representatives to be split evenly between district and ITC fiscal staff.
This will ensure end-users have direct input into software development decisions. To this end, members have also created three working groups that focus on prioritizing development, creating reports and organizing training support and documentation efforts.
</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">How will recent fiscal agency and leadership changes affect the development of Redesign?</span></span><o:p></o:p></p>
<p class="cs557ef5b0"><span class="cs1e88c66e1"><span style="font-size:10.0pt">On July 1, 2019 the Management Council assumed fiscal agency responsibilities for State Software and Matt Calmes became Director of the SSDT. These developments promise continued
steady growth in the Redesign that will provide a path away from the brittle Classic system. No changes to the development timelines cited previously are anticipated. With the additional funds cited above, the Management Council will work with the SSDT to
augment existing programming, infrastructure and support resources over the course of the current fiscal year. This staffing, combined with continued support from ODE, the Management Council’s resources, the support of all of the state’s Information Technology
Centers, and guidance from the State Software Advisory Committee bode well for the continued success of Redesign.</span></span><o:p></o:p></p>
<p class="cs157f42b2"><span class="cs1ba52a261"><span style="font-size:10.0pt">Current Redesign Adoption Map-
</span></span><span class="cs1e88c66e1"><span style="font-size:10.0pt">See file attachment</span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1e88c66e1"><span style="font-size:10.0pt"> </span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1e88c66e1"><span style="font-size:10.0pt">Respectfully,
</span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1e88c66e1"><span style="font-size:10.0pt"> </span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1ba52a261"><span style="font-size:10.0pt">State Software Development Team (SSDT) and</span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1ba52a261"><span style="font-size:10.0pt">Office of Field Relations, Ohio Department of Education</span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="cs1e88c66e1"><span style="font-size:10.0pt"> </span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="csadfa96c31"><span style="font-size:10.0pt"><a href="mailto:fiscal.redesign@ohio-k12.org">fiscal.redesign@ohio-k12.org</a></span></span><span class="cs1e88c66e1"><span style="font-size:10.0pt">
</span></span><o:p></o:p></p>
<p class="cs2654ae3a"><span class="csedbfcf261"><span style="font-size:8.0pt"> </span></span><o:p></o:p></p>
</div>
</body>
</html>