1. Administrative Advance Update – Department of Information Technology August 6, 2012

2. Agenda 1.Start of School Status 2.Student Registration Changes 3.True Time Issues 4.Infrastructure Upgrades 5.Computer Refresh – Summer 2013 6.Tablet Procedures

3. Start of School Status Elementary Schools

4. Start of School Status Secondary Schools

5. Student Registration Changes Process 1.ADM Count date – last Friday in September 2.15 day Correction Period 3.Signoff on final student count 4.Audit in May resulted in 13.7 fewer students and a loss of over $66,000

6. Student Registration Changes

7. Operating Procedures 1.The count date will be the district’s final count number as agreed to by the state DOE and the superintendent. 2.Final count number is immutable. No changes will be made that will affect the official count number. 3.Enrollment errors will be corrected as of the date discovered with appropriate annotations made to accurately reflect the scenario. 4.Skyward release will prevent secretaries from changing enrollment or withdrawal dates to an earlier date. 5.IT will run monthly reports to guarantee count number holds.

8. True Time Issues Background The software is programmed to exclude Time Sheets with notes from the Mass Approval process. This is because the supervisor should individually review the notes for impact to the approval process Solution After using Mass Approval to approve time sheets, those with comments will remain in your queue for approval. Individually approve/deny the remaining time sheets as appropriate …. OR … tell your staff not to use notes!

9. 2012-2013 Technology Upgrades Current 3Com Switches –Over 12 years old –Unmanaged / Unreliable –Communication speeds vary between connections New HP Switches –Elevate known issues –Managed remotely / Better service –Prepare for enterprise wireless connections Elementary Switch Upgrades

10. Technology Refresh & Planning November - Form Factor Showcase

11. Technology Refresh & Planning January 4 – Budget and Staff / Student Counts January 14 thru February 1 – Building Team Meetings February 22 – Student Allocation Selections Deadline April 1– Bid to Prospective Vendors Event Timelines

12. Technology Refresh & Planning Thin Clients All LCD Monitors Leased Equipment Buyout Considerations

13. Tablet Procedures Guiding Principles 1.Devices are not true computers a.Cannot join the schools network domain (policies, mgmt, etc.) b.Don’t run traditional programs and curriculum c.Closed architecture; not designed for maintenance d.Support limited to network connections & app restoration e.Susceptible to damage/breakage/loss f.Unknown lifecycle 2.District has not standardized on a single device; solution must support Android & iOS environments

14. Tablet Procedures Guiding Principles (continued) 3.Purchased applications need to be auditable & manageable a.Consumer App stores are consumer centric and require individual logins b.Purchased by normal approval process c.Apps need to belong to district with ability to audit license counts and issue/retract licenses 4.Teachers will need training on educational best practices a.Classroom management b.Educational apps that align and support district initiatives c.Collaborative culture needs time to grow and develop

15. Tablet Procedures Process & Procedures Procurement 1.Purchase orders request tablets from Technology CatalogTechnology Catalog 2.Tablet orders will include Insurance (function, damage, loss) 3.Tablets shipped to IT Office (CSAC) a.Insurance policy registered b.Tablets configured with default applications & network config

16. Tablet Procedures Process & Procedures (continued) App Purchase 1.Users will not purchase apps with district PCards 2.Apps requested via App Purchase FormApp Purchase Form 3.IT Office places order via the District App Store a.Integrates with Google Play or iTunes Stores b.Android apps are distributed automatically from app store c.iOS apps installed by downloading licensing spreadsheet from Apple’s VPP program and manual import to app store for distribution

17. Tablet Procedures Process & Procedures (continued) Maintenance & Support 1.Network connections and app installation, call Help Desk 2.Unit malfunction or breakage, use claim form on website.

18. Questions/Comments?