Charter

Purpose

This document formally establishes Rygen Technologies’ Artificial Intelligence Management System (AIMS) in accordance with ISO/IEC 42001:2023. The AIMS serves as the governance and operational framework to ensure responsible, transparent, and effective development, deployment, and use of AI systems across Rygen’s platforms and internal operations.

Scope

The scope of the AIMS is defined in the “Scope of the AIMS” document and includes:

• All AI-powered features in the TMS and IPaaS
• AI-driven internal tools
• Models and logic built in-house, integrated via third-party APIs, or managed open-source components
• All teams contributing to AI development, deployment, governance, or monitoring

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
• Enable consistent application of policies, risk assessments, and reviews across AI projects
• Support continual improvement through feedback, monitoring, and governance

Structure of the AIMS

The AIMS consists of:

• AI Policy and Governance Documents (e.g., AI Policy, Roles and Responsibilities, Scope, Process Frameworks)
• Process Controls and Practices (e.g., Risk Assessment, Model Lifecycle, Impact Assessments, Monitoring, Audit)
• Oversight Bodies (Principal AI Engineer, CTO, AI Governance Committee)
• Lifecycle Integration: Integrated 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 acts as executive sponsor, ensuring strategic alignment and resource allocation.
• Team leads ensure compliance within their domains.
• The AI Governance Committee provides multi-disciplinary review, approval, and oversight of AI system risk, ethics, and incidents.

(See “Roles, Responsibilities, and Authorities of the AIMS” for full definitions.)

Documentation and Recordkeeping

The AIMS and its supporting processes and documentation are managed in:

• Gitlab: System policies, procedures, and records
• Jira: Implementation tracking and corrective actions
• Confluence: Meeting minutes and collaborative decisions

Documented information shall follow version control, change approval, and retention rules defined in Clause 7.5 of the standard.

Continual Improvement

The AIMS will be reviewed and improved on an ongoing basis through:

• Quarterly Governance Reviews
• Monthly progress reports from the AI lead to the CTO
• Corrective action process for nonconformities
• Feedback from audits, users, and stakeholders

Revision History