SOP · Partners · The Cognition Factory
Enterprise Deployment SOP
Standard process for deploying HAL-E and AAE in enterprise and institutional environments — consistent quality, clear accountability, and client-owned success criteria.
1. Purpose
Define how implementations are run so organizations get the same methodological discipline whether the goal is upskilling, competency validation, or knowledge architecture.
2. Scope
Applies to:
- Mid-to-large organizations deploying HAL-E and/or AAE internally
- Educational institutions aligning maps to programs or published skill pathways (no TCF accreditation claim)
- Consulting and professional services firms embedding systems into client delivery
Does not cover individual or very small team deployments (under ~10 users), which use a lighter process.
3. Deployment models
Managed deployment
Full implementation support. Typical scale 50–500+ users. Higher customization; dedicated success manager.
Guided self-deployment
Strong internal technical capability. Typical scale 20–150 users. Medium customization; shared support and training.
4. Implementation phases
Phase 1 · Discovery & alignment (1–2 weeks)
Stakeholder interviews, current-state assessment, success criteria, target domains, technical environment review, deployment model finalization.
Phase 2 · Configuration & integration (2–4 weeks)
Domain and competency model configuration, cartridge development, SSO / identity integration, data import strategy, pilot environment.
Phase 3 · Pilot & validation (2–3 weeks)
Limited cohort rollout, telemetry, friction identification, success criteria check, Go/No-Go.
Phase 4 · Full rollout & enablement (3–6 weeks)
Staged expansion, admin and end-user training, internal support processes, knowledge transfer.
Phase 5 · Handover & partnership
Steady-state operations, review cadence, updates access, escalation paths.
5. Roles and responsibilities
The client retains accountability for business outcomes and internal coordination. The Cognition Factory provides technical leadership, integration support, and methodological guidance through the engagement.
6. Success metrics (client-defined in the SOW)
Metrics below are examples of what a SOW may instrument. Targets and interpretation belong to the client. Improvement on a practice pack is not a certification or employment credential.
- Adoption — active usage and session frequency
- Practice signal — assessment improvement and error-rate reduction over time (within the engagement)
- Continuity — stability on re-assessment at agreed intervals (e.g. 30/60/90 days)
- Client business measures — only where the SOW names them and the client owns the data
- Operational health — support volume and time-to-resolution against contracted response
7. Common failure modes & mitigation
Risks include low adoption (weak change management), early over-customization, weak systems integration, “set and forget,” and unrealistic time-to-value. Mitigations: executive sponsorship, disciplined scoping, thorough Phase 1 discovery, named internal ownership, honest timelines.
8. Change control
Material changes to scope, success criteria, or technical requirements after Phase 1 go through formal change request. Minor configuration during pilot and rollout follows the normal project cadence.