Ascentia is a connected product portfolio for student lifecycle management, modern learning, skills-based recruitment and mobility, and education and workforce decision intelligence.

The portfolio contains Ascentia SLMS, Ascentia Learning, Ascentia Recruit, and Ascentia IOC. Each product has a specialist responsibility and can be introduced independently or connected over time.

No. The architecture uses separate product responsibilities and federated systems of record. Controlled integrations connect authorized information without allowing every application to edit the same business facts.

No. A customer may begin with one product, add other products later, or integrate approved existing systems where replacement is unnecessary.

The initial market hypothesis includes education and training providers, vocational and workforce programs, recruitment and mobility organizations, employers, and bounded government or multi-institution programs. Fit must be validated through discovery.

SLMS manages institutional candidate and learner lifecycle, admission, enrollment, attendance, assessment, academic records, student services, progression, communication, and related institutional operations.

No. It is not currently positioned as a complete finance, payroll, HCM, research, grants, or higher-education ERP replacement.

Ascentia Learning manages courses, learning paths, content, detailed learner activity, progress, learning assessment, competencies, certificates, authoring, and learner analytics.

The implementation contains tested Moodle backup and SCORM import paths. Compatibility depends on Moodle version, plugins, activities, H5P, packages, files, media, links, data, and rights. A representative assessment is required; universal migration is not promised.

Recruit combines candidate and employer workflow with an evidence-aware Skills Passport, explainable eligibility and matching analysis, trainable-gap identification, contracts, deployment, and placement-specific mobility operations.

No. Current ESCO-oriented normalization uses a partial curated vocabulary. Official coverage, languages, local mappings, and occupation domains require further implementation and validation.

IOC is an education and workforce decision-intelligence product that consumes governed signals from operational systems and supports analytical views, maps, alerts, missions, decisions, tasks, and outcome monitoring.

Not universally. IOC contributes education and workforce domain models, Ascentia integrations, missions, and workflows. It can coexist or integrate with customer-standard data, BI, GIS, and enterprise platforms.

AI may assist learning support, content creation and tagging, text structuring, grounded exploration, briefing, and explanation. Enabled functions, providers, data, evaluation, and controls vary by product and deployment.

No. Recruit’s documented matching logic keeps deterministic eligibility and scoring separate from AI text assistance. Authorized people remain responsible for hiring, regulated skill validation, immigration, academic, and public decisions.

No such claim is made. Quality and fairness must be evaluated for the specific model, data, language, population, occupation, task, and decision context, with appropriate human oversight and correction processes.

AI can assist drafts and metadata, but academic and content owners remain responsible for accuracy, rights, suitability, assessment validity, and publication.

Local-first and optional-provider patterns are represented, but available models, disablement, local hosting, data restrictions, fallback, and support must be confirmed for the selected product and deployment.

No universal certification or compliance statement is approved. The implementation represents multiple security and governance controls, but each deployment requires legal, security, privacy, architecture, and operating-effectiveness review.

The proposed licensing framework treats customer operational data as customer-controlled under the applicable agreement and law. Final ownership, controller and processor roles, permitted use, retention, deletion, and export must be defined contractually.

No. Institutional processing, learning, recruitment, employer disclosure, IOC analytics, and hosted AI can involve different purposes and legal bases. Authorization should be purpose-specific.

The target Recruit model keeps mentioned, inferred, and verified skills separate and retains source and evidence status. An inference should not silently become a verified fact.

No. Public contact and demonstration forms should not accept CVs, student or candidate records, credentials, health or immigration data, confidential customer records, or security vulnerability details.

Yes, through supported APIs, events, adapters, imports, files, or controlled read gateways where an approved contract exists. Connector version, fields, authentication, purpose, retry, monitoring, correction, and support must be specified.

No. Ascentia’s strategy is to integrate, migrate, or coexist according to the desired outcome and the system that should remain authoritative.

It depends on the supported connector and deployment. Refresh frequency should be stated explicitly; real time is not used as a universal claim.

Migration normally includes source inventory, profiling, mapping, rights and privacy review, trial loads, transformation, reconciliation, exceptions, acceptance, cutover, rollback, and post-cutover validation.

The strategic framework proposes Ascentia-managed cloud, dedicated private cloud, customer-managed cloud or on-premises, and specially approved restricted environments. Availability is product-, release-, country-, and architecture-specific.

No universal claim is approved. Sovereign, disconnected, or restricted deployment requires a validated product profile, local dependencies, entitlement, release, patch, support, maps and data, and AI decisions.

Responsibility depends on the contracted deployment. Every project should define infrastructure, network, application, identity, data, backup, recovery, monitoring, incident, integration, and support ownership in a responsibility schedule.

The current proposal uses annual product subscriptions or term licences, independently identifiable products, a primary scale metric per product, separate implementation services, and deployment and support options. Final commercial packages and prices are not yet approved.

Not yet. Discovery is required to determine products, scope, scale, deployment, migration, integrations, AI, implementation, and support before a proposal can be prepared.

The draft framework proposes active learner bands for SLMS and Ascentia Learning, named recruiter or case-manager seats for Recruit, and mission or platform scope for IOC. These require commercial approval.

Implementation, migration, integration, training, managed operations, and enhanced support are expected to be scoped separately unless an approved package states otherwise.

Begin with a bounded journey, migration, occupation corridor, or decision mission. Define owners, users, systems of record, evidence, data, integrations, controls, baseline, and desired outcome before selecting the product configuration.

No universal timeline is approved. Duration depends on product scope, data, migration, integrations, configuration, deployment, security review, customer availability, training, acceptance, and change management.

A time-boxed pilot or evaluation is a proposed commercial model. It requires defined scope, data class, users, success criteria, expiry, conversion path, and no implied production service level.

Standard, enhanced, mission-critical, managed-application, and customer-managed options are proposed. Service levels are not available until staffing, monitoring, escalation, resilience, and recovery are validated for the deployment.

No. Ascentia can help establish workflows, evidence, and measurement, but education, employment, immigration, institutional, and policy outcomes depend on many parties and conditions.