Why this exists
Device management and classroom support require high-velocity operational tooling. This initiative focuses on the workflows technicians use every day, ensuring data accuracy, clear interfaces, and minimal manual reconciliation.
March 2026 Registry Reconciliation
The updated BOUSD registry made the device-operations stack easier to describe as one system:
- the staff dashboard and refresh portal now read as a shared scheduled workflow instead of isolated spreadsheets;
- the Mosyle API component is separated from the live bidirectional Mosyle and Snipe-IT reconciliation workflow;
- Munki endpoint configuration is linked more clearly to the broader refresh and inventory ecosystem instead of standing alone as a local script page.
Asset and Inventory Authority Notes
- Mosyle remains authoritative for live MDM/device-state telemetry used by endpoint operations.
- Snipe-IT remains authoritative for asset inventory and asset-tag governance where district policy treats it as the inventory system of record.
- Munki Client Identifier automation is an endpoint-local enrichment and targeting workflow, not an inventory authority.
- Reconciliation workflows exist to reduce drift between systems, but precedence details for edge cases still need a documented policy and validation.
Measures of success
- Technicians can complete refresh workflows without manual data cleanup.
- Device inventory and assignment data stay aligned with source systems.
- Classroom and device support tools have clear ownership and update cadence.
- Operational interfaces remain usable under daily workload pressure.
Active projects
- Staff Device Refresh Operations Portal
- BOUSD-Staff-Technology-Dashboard
- Classroom Display Refresh Coordination
- Aeries Staff Extract SQL Generator
- Mosyle to/from Snipe-IT Asset and Tag Sync
- MDM Integration Automation (Mosyle)
- Munki Client Configurator
- Snipe-IT Asset Ops Automation
Key risks
- Stale inventory or staff extracts cause incorrect assignments and worklists.
- Mapping-file governance drifts without clear ownership.
- Tooling becomes too complex for frontline operators if workflow and component layers are not documented separately.
- Status write-back rules stay informal and become support debt during refresh campaigns.