IT-SVCS · K-12 Systems Engineering
Innovatory Tech Services shares practical, sandbox-tested know-how for K-12 IT, focused on connecting identity, devices, and data across Google, Microsoft, and Active Directory using the tools districts already have.
it-svcs.org
The knowledge base is where most of the work lives: self-help guides, informational write-ups, and scripts, each built and tested in a sandbox before it's published. It's free for any district to use.
Have a topic you'd like researched or a guide that could be clearer? Let me know. That feedback shapes what gets written next.
Schools as critical infrastructure
A school district isn't a small office with a lot of laptops. Education facilities are already counted among the nation's critical infrastructure, and from a technology standpoint a district behaves like any large enterprise: thousands of users, many sites, regulated data, and systems that can't go down when the bell rings. That's why I see the work as engineering those systems, not just supporting them.
Complex enterprise system (n.): a socio-technical system of systems in which people, processes, information, and technology (both IT and OT) work toward a shared mission across many sites and stakeholder groups. Its component systems run largely on their own yet depend on one another. No one controls the whole from a single point, its behavior emerges from how the parts interact, and it has to keep running while it changes.
Informed by W. B. Rouse, Universities as Complex Enterprises (Wiley, 2016); A. Gorod et al., eds., Case Studies in System of Systems, Enterprise Systems, and Complex Systems Engineering (CRC Press, 2014); and D. Giachetti, Design of Enterprise Systems (2010).
Identity and access, student and staff devices, SIS, HR, and finance data, networks and cloud platforms, plus the compliance that wraps them, like student privacy law, internet filtering requirements, and state testing.
The systems that keep campuses physically running and safe: door access, cameras, bells and PA, emergency notification, HVAC, lighting, and energy controls. They're increasingly networked, which makes them increasingly IT's concern.
Rouse describes academic enterprises in layers that enable or constrain one another. The same layers fit a school district.
The daily work of teaching, learning, and support: what happens in classrooms, offices, and at the help desk.
Enrollment, account provisioning, device lifecycles, testing windows: the workflows that connect people to systems.
Sites, departments, governance, and budgets: who owns which decisions and how resources are allocated.
State and federal rules, funding, vendors, county offices, and the community: forces outside the district that shape everything inside it.
How I work
No two districts run the same mix of platforms, people, and history. These are the principles behind every design and every guide in the knowledge base.
Every design starts from the district's own reality: its platforms, staffing, budget, and the way teachers and students actually work. Templates come last, if at all.
Most districts already own more capability than they use. Get the most from existing licenses and free tools before spending public money on something new.
Identity, devices, data, and people are one connected system. A change in one place ripples everywhere, so each piece is designed to strengthen the others.
Good design outlasts its designer. Everything is documented so the people who run it every day understand it, can maintain it, and aren't dependent on any one person.
Frameworks are guides, not rulebooks. I scale them down to what a small district can actually sustain.
{{s.desc}}
Who it's for
Small and mid-size districts, up to roughly 2,400 students and 300 staff, are the easiest place to put these ideas into practice. They're big enough to need enterprise-grade systems and small enough to move quickly.
The same principles hold at any size. Larger districts usually carry more technical debt and turn a bigger ship politically and operationally, so the work is more deliberate and phased, but the destination is the same.
Whether you run Google, Microsoft, or both, the goal is one coherent environment your team understands and can maintain on the budget you actually have.
Areas of focus
Design comes first: get the most out of the platforms and licenses a district already pays for, and reach for free or low-cost options before any new spending.
Identity designs built on what you already run: Active Directory, Entra ID, Google Workspace for Education, and free sync tools like Google Cloud Directory Sync. Clear sources of authority and scripted provisioning from enrollment to exit, before buying another identity product.
Management designs that use the Intune and Chrome Education licensing you may already have, plus built-in Windows tools like provisioning packages. Covers reimaging, naming and OU structure, and secure state-testing setups without third-party add-ons.
Data flows designed around what's included: your SIS's built-in exports, Microsoft School Data Sync, and open standards like OneRoster and Ed-Fi. Where no connector exists, scripted SFTP pipelines can fill the gap, with any per-export vendor fees weighed up front.
For anything that doesn't fit a box: a second set of eyes on a plan, a workflow that needs untangling, or a question about where to start. The goal is always a practical design built from what you already have.
* Services aren't publicly offered at this time. For now, the focus is maintaining the knowledge base of self-help guides and informational resources at it-svcs.org.
Who I am
In the Marine Corps I served as a Transmission Systems Operator. The job was a lot more than radios: it meant keeping communications up across every layer, from the physical links and transmission equipment to the networks and the services riding on top of them. When one layer failed, everyone downstream felt it.
That way of thinking came with me into K-12 IT, where I focus on how a district's complex enterprise systems are designed and built. Innovatory Tech Services is my disabled-veteran-owned small business and passion project.
I'm also a family man and a lifelong lover of all things technology. The knowledge base is my way of sharing what I've learned with the people who keep schools running every day.
For the love of the game
The guides are free and will keep coming no matter what. If one saved you an afternoon, a coffee provides the caffeine to maintain the testing labs and hosting behind every guide. Completely optional, always appreciated.
Contact
Questions about a guide, feedback on the knowledge base, or a topic you'd like researched? Send a note. I'll respond as time permits.