Charter
Purpose
This charter establishes Rygen Technologies’ AI Management System (AIMS) under ISO/IEC 42001:2023. The AIMS is the framework Rygen uses to develop, deploy, and use AI systems responsibly across its platforms and internal operations.
Scope
The scope of the AIMS is defined in AI-003: Scope.
Objectives of the AIMS
- Ensure AI is developed and used in a trustworthy, safe, and compliant manner
- Align AI practices with business strategy and risk tolerance
- Apply policies, risk assessments, and reviews consistently across AI projects
- Support continual improvement through feedback, monitoring, and governance
Structure of the AIMS
The AIMS consists of:
- AI policy and governance documents, such as the AI Policy, Roles and Responsibilities, and Scope
- Process controls, such as risk assessment, impact assessment, the system lifecycle, monitoring, and audit
- Oversight by the Principal AI Engineer, the CTO, and the AI Governance Committee
- Integration into Rygen’s Agile, DevOps, and product lifecycles using Jira, GitLab, and Confluence
Authorities and Responsibilities
- The Principal AI Engineer owns and operates the AIMS.
- The CTO is the executive sponsor and ensures strategic alignment and resources.
- Team leads ensure compliance within their domains.
- The AI Governance Committee provides multi-disciplinary review and oversight of AI system risk, ethics, and incidents. Approval rests with the authorities each procedure names, listed in AI-005.
AI-005: Roles and Responsibilities gives the full definitions.
Documentation and Recordkeeping
The AIMS documentation is kept in:
- GitLab: policies, procedures, records, and meeting minutes
- Jira: implementation tracking and corrective actions
- Slack #ai-governance: committee discussion and decision threads (AI-019)
Documented information shall be controlled under AI-006: Document Control.
Continual Improvement
The AIMS is reviewed and improved through:
- Management reviews (AI-012)
- The corrective action process for nonconformities
- Feedback from audits, users, and stakeholders
Revision History
| Version | Date | Author | Summary of Change |
|---|---|---|---|
| 1.0 | 2025-06-05 | Field Bradley | Initial draft. |
| 1.1 | 2025-09-02 | Field Bradley | Migrated to markdown and gitlab |
| 1.2 | 2026-07-14 | Field Bradley | Governance review cadence changed from quarterly to every four months (AI-1759) |
| 1.3 | 2026-11-04 | Field Bradley | Removed monthly progress reports to the CTO, which are not done; the four-monthly review is the management review (AI-2173) |
| 1.4 | 2026-11-05 | Field Bradley | Shortened the charter, with the scope, approvals and management review cadence cited from AI-003, AI-005, AI-006, AI-012 and AI-019 (AI-2173, AI-2131). |