[et_pb_section fb_built=”1″ _builder_version=”4.24.3″ global_colors_info=”{}”][et_pb_row column_structure=”2_3,1_3″ custom_padding_last_edited=”on|phone” _builder_version=”4.24.3″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” custom_padding=”20px||||false|false” custom_padding_tablet=”30px||||false|false” custom_padding_phone=”20px||||false|false” global_colors_info=”{}”][et_pb_column type=”2_3″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.24.3″ header_font=”Open Sans||||||||” header_font_size=”24px” header_line_height=”1.2em” header_2_font=”Open Sans||||||||” header_2_font_size=”24px” header_2_line_height=”1.2em” header_4_font=”Open Sans|700||on|||||” header_4_text_color=”#ff7435″ header_4_font_size=”17px” header_4_letter_spacing=”1px” header_6_font=”Open Sans||||||||” header_6_font_size=”18px” background_size=”initial” background_position=”top_left” background_repeat=”repeat” hover_enabled=”0″ header_font_size_tablet=”24px” header_font_size_phone=”24px” header_font_size_last_edited=”on|desktop” header_2_font_size_tablet=”24px” header_2_font_size_phone=”20px” header_2_font_size_last_edited=”on|phone” header_6_font_size_tablet=”” header_6_font_size_phone=”” header_6_font_size_last_edited=”on|desktop” use_border_color=”off” global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n
<\/span><\/p>\n Lexington City Schools, located in Lexington, North Carolina, was spending about 175 hours per year of IT staff time simply typing\u00a0updates to their school network directory system. Part of Lexington\u2019s vision is to integrate technology into all classes in every school and to use data to individualize instruction for all students. Digital learning systems\u00a0must have\u00a0up-to-date student data and have login credentials for the school’s internet and network. The challenge for all school districts\u00a0is that the inflow of new students and data changes are continuous.<\/p>\n <\/p>\n In Lexington’s case, a new student was first entered into their Student Information System (PowerSchool) and then had to be reentered into Microsoft Active Directory to enable The decision to adopt an automated solution was based on needed improvements in three areas:<\/p>\n 1.\u00a0\u00a0Eliminate<\/strong>\u00a0<\/b>Lost Seat Time<\/b> for new students: New students typically waited from 1 to 3 weeks to 2.\u00a0\u00a0Recover Staff Time<\/b>: Lexington on\u00a0a weekly basis would experience a combination of 30\u00a0student accounts being created, updated or\u00a0deleted. \u00a0Data change was requiring a minimum of\u00a0175 staff hours per year just to make the data changes manually in Active Directory; this was valuable staff hours that could better be deployed elsewhere.<\/p>\n 3.\u00a0\u00a0Data accuracy<\/b>: The 175 hours of manual data entry changes each year left room for error. Lexington wanted to be sure all data entered into Active Directory was correct.<\/p>\n <\/p>\n ReadWrite Digital helped Lexington replace its manual process for data updates with one\u00a0fully automated using Integrator<\/em>. Every hour, ReadWrite Digital\u2019s cloud-based Integrator<\/em> software accepts student records from PowerSchool, searches for changes, and pushes updated student data into Lexington\u2019s Active Directory. Almost as soon as new students are entered into PowerSchool, they are able to log into Active Directory, thus nearly eliminating waiting time to access instructional content.<\/p>\nNeeded Improvements<\/strong><\/h6>\n
No More Time Wasted<\/strong><\/h6>\n