Wednesday, August 28, 2013

Writing Policy


Okay, i am techie. I don't like writing policies. Its simple as that. I find policies difficult. Not necessarily to write, but to find the balance the institutions requirements along with the "humans" who will be interacting with the things which i'm writing policy. My human side always plays the what-ifs. the grey areas. ugh.

So, we are writing our lost and stolen and replacement device policy. Finance liked it minus some Financial language! easily remedied. waiting on legal and HR. Something about with holding a last paycheck until we get our gear back. The goal is to either get our gear back or withhold the cost of the units said staff member failed to return. Simple enough. However, that means our paperwork has to be in order. teacher A is owner of laptop X and ipad y. Fun! more paperwork! (yes, we have tools to tie the devices to the users. YEAH KACE!).




Week 1 Totals

Well, I ran our last 7 days of work orders totals. OMG! Wow.

1240 work orders closed in a week.
High water was around 1000 open work orders
current total is around 650 open requests
highest daily request was 400 work orders. doing the total on this day was sad. we close 275 requests and got 400.

(for those of you who don't know the pattern of k-12..here goes. In early June, turn everything off and store it...somewhere. and that somewhere is likely only conditioned down to 90-95 degrees. then, in the last week of august, find said stored items. turn them on and hope they work. Remember, some of the teachers turning these items on don't "know" technology. its a magic box. we are ok with that. getting the little 2nd grader to complete a task can be magic to me too. she does her magic with the kids, my team does our magic with the devices).

Thats pretty good from what for us. 38 sites, 3500 staff users. new ipads. We have a pretty good support staff who understands getting everyone up and running is job 1. We are on the second wave of requests, its works, but i can't do X. Access youtube, run adobe pro, etc. these are the more complex problems where unfortunately "no" becomes an answer.