Req 2.94: The Supplier shall support DepEd in establishing a...

⚙️ Technical Demonstration

IMTLazarus completely satisfies this requirement by providing the functional tooling and operational alignment necessary to establish a rigorous, audited Change-Management Framework. This structure governs the entire lifecycle of DepEd’s MDM environments—from initial policy design to department-wide maintenance—minimizing configuration drift and preventing unauthorized or disruptive modifications to the fleet.

The framework operates across four sequential, mandatory phases:

• 1. Creation & Staging: Configuration changes, web filtering exceptions, or system rules are drafted within isolated, non-production policy containers. Administrators map the proposed changes to test groups (Organizational Units) rather than deploying them live to the production environment.
• 2. Multi-Tier Approval Workflow: Aligned with Role-Based Access Control (RBAC), proposed configuration modifications must be reviewed and signed off by authorized Policy Approvers. The platform logs the administrative identity, timestamp, and justification for the change before it can be pushed to production.
• 3. Controlled Rollout & Canary Testing: Policies are deployed progressively using a staged rollout methodology (e.g., piloting the rules inside a single Schools Division or school tier first). System telemetry is actively monitored to evaluate device stability and rule efficacy before wide-scale activation.
• 4. Maintenance & Immutable Auditing: Once a policy goes live department-wide, the system continuously tracks its enforcement status. The platform’s version-control mechanics log every subsequent modification, providing a comprehensive, exportable audit trail for governance compliance.

---

Change-Management Lifecycle Matrix

To ensure programmatic consistency across Central, Regional, Division, and School administrative levels, the following procedural lifecycle defines the change management workflow:

Phase	Operational Gate / Milestone	Responsible Governance Role	System Action / Control Mechanism
Phase 1: Initiate	Request & Drafting	Configuration Manager	Create policy draft inside a designated Sandbox Profile; define scope and target OUs.
Phase 2: Evaluate	Technical & Safeguarding Review	Safeguarding Reviewer / IT Lead	Audit filter exceptions against DepEd compliance guidelines; check for cross-platform conflicts.
Phase 3: Approve	Formal Authorization Sign-off	Policy Approver	Commit the approved configuration to the version history database; generate a deployment token.
Phase 4: Pilot	Canary Testing & Verification	Configuration Manager	Deploy to a restricted pilot device group; monitor real-time activity logs for unexpected blocks.
Phase 5: Deploy	Production Rollout	Configuration Manager	Execute zero-downtime, over-the-air (OTA) push across the targeted nationwide fleet.
Phase 6: Audit	Maintenance & History Logging	Reporting Administrator	Generate compliance reports; preserve historical version snapshots for single-click rollback readiness.