Skip to content
Companionby MetaControl
Admin panel

METACONTROL / RESEARCH & DEVELOPMENT

Planned · Seeking IRAP support and a pilot institution

R&D project: Intelligent University

Reliable coordination for university administrative processes, from a conversational request to a verifiable outcome.

Higher education is the first proposed application domain of the MetaControl platform, not the boundary of the platform.

THE PROBLEM TO INVESTIGATE

A simple request can cross a complex institution.

A student or staff member should not need to know every departmental system to express an administrative need. The proposed screen-independent experience starts with conversation, while valid action still requires clear rules, responsibilities, permissions and actual task state.

Open R&D question

Can a shared runtime accommodate institution-specific process variations at university scale while maintaining stable, controlled and verifiable execution? This is a hypothesis to test, not a claim of demonstrated university-scale performance.

An existing service catalog or API integration alone does not answer this question. The project must evaluate rule variation, incomplete inputs, execution failures and required human approvals in selected workflows.

An illustrative evaluation scenario

“I want to follow up on my academic request.” The workflow below needs testing with authorised information and real responsibility assignments. It is an illustration, not live execution or a pilot result.

  1. 1Express the need
  2. 2Clarify & check access
  3. 3Approve & route
  4. 4Verify & follow up

People retain a role in sensitive decisions. An uncertain outcome must not be presented as a completed action.

DOCUMENTED · CATALOG SCOPE, NOT OPERATIONAL ACCEPTANCE

65 services. Six service areas for one institution.

This map organizes registered services around their users. The six areas are a presentation grouping, not six independent products or deployed systems. A catalog entry does not establish live execution or customer acceptance.

12 catalog services

Academic journey & learning

Students, faculty and academic offices

  • Academic guidance
  • Academic policies
  • Academic references
  • Academic structure
  • Admissions
  • Course offerings
  • Course registration
  • Enrollment
  • Content
  • Learning content
  • Learning paths
  • Skill standards
8 catalog services

Assessment & progress

Faculty, assessors and students

  • Assessment
  • Assessment delivery
  • Assignments
  • Attendance
  • Credentials
  • Legacy exam compatibility
  • Gradebook
  • Question bank
10 catalog services

Coordination & support

Students, families and service teams

  • Classrooms
  • Committees
  • Communications
  • Documents
  • Guardians
  • Notifications
  • Office workflows
  • Scheduling
  • Support
  • Work planning
6 catalog services

Organization & people

Institution leaders and HR

  • Employment opportunities
  • Freelance engagements
  • Human resources
  • Institutions
  • Party records
  • Staff compensation
16 catalog services

Finance, resources & procurement

Finance, procurement and operations

  • Asset lifecycle
  • Customers
  • Facilities
  • Finance
  • Financial accounts
  • Financial aid
  • Order fulfillment
  • Point of sale
  • Pricing
  • Procurement and assets
  • Product catalog
  • Resource capacity
  • Resources
  • Sales
  • Suppliers
  • Tuition
13 catalog services

Access, data & service quality

System, data and oversight teams

  • Page permissions
  • Access roles
  • Access scopes
  • External references
  • File storage
  • Geographic references
  • Identity references
  • User directory
  • Integration
  • Monitoring
  • Page presentation
  • Reporting and analytics
  • Security

From service scope to evidence of results

Proposed example: enrollment request → check academic conditions and access → check tuition and scheduling → responsible person approves → record and notify. This combination is an evaluation scenario; proving it requires result readback from the responsible service, failure testing and human acceptance.

What is being assessed?What evidence is needed?
Service coverageRegistered catalog: 65 entries across six areas.
Current operationStatus, date, scope and limits for each capability in the evidence record ↗
University-scale executionR&D and pilot plan; no accepted university-scale result is announced.

PROPOSED PLAN — NOT AN EXECUTION COMMITMENT

A 5–7 month plan with evaluation gates

The proposed duration depends on scope, resources and host-institution agreement. The target is one pilot at one institution; no contracted pilot institution or letter of intent is announced here.

Months 1–2, proposed

1 · Scope & baseline

Select workflows, document variation and the existing baseline, and agree acceptance criteria and data-use rules.

Months 3–4, proposed

2 · Develop & experiment

Test selected workflows, exceptions and recovery; record results and conduct human review before expanding scope.

Months 5–6, proposed

3 · Bounded pilot

Run a bounded pilot with an agreeing institution, compare against the baseline and document readiness and next-step decisions.

By month 7, proposed

4 · Evaluate & decide

Review evidence against agreed criteria and document a readiness, revision or stop decision.

Proposed success measures

MeasureEvaluation approach
Correct completionRead the result from the responsible service and compare with the expected outcome.
Access & approvalTest refusal of unauthorised actions or missing approvals; proposed acceptance target: zero unauthorised actions in the agreed test set.
Failure & recoveryTest exceptions, uncertain-outcome handling and duplicate prevention.
Service time & costCompare with the same workflow’s baseline; agree thresholds before the pilot.

Current evidence, separate from future plans

Recorded status

Platform capabilities

The capability record provides status, date, test scope and limitations. It does not establish completion of the university R&D project.

Concept demonstration

University showcase

lms.ir presents the platform’s first application domain. Its scenarios are not evidence of customer-accepted deployment.

Evidence required

Market validation

A pilot, letter of intent or documented customer interviews need separate validation. Unverified customers, revenue or pilot outcomes are not asserted here.

PLAN — NOT REALISED IMPACT

R&D and commercialization from Canada

The proposed 5–7 month period has three planned workstreams: development and testing, pilot evaluation, and commercialization preparation. The intended direction is R&D and employment development in British Columbia, with commercialization from Canada. Hiring numbers and timing are being developed and are not announced as commitments.

This page does not claim NRC IRAP endorsement, approval or funding. Technical and commercial assessment and any support terms are separate matters.

Discuss the product and the project

This public outline supports an introductory review. Detailed technical and commercial information is handled through an appropriate private review process.

sales@metacontrol.live ↗Company identity & contact ↗