Scope
Purpose
This document defines the boundaries and applicability of Rygen’s AI Management System (AIMS) and specifies which parts of the organization, products, and operations are governed by it.
Scope Statement
Rygen’s AI Management System (AIMS) applies to the AI systems for Logistics SaaS services which Rygen provides.
Scope Exclusions
The following are out of scope for the current AIMS implementation:
- Non-AI software modules with no AI dependencies.
- Third-party SaaS services integrated via API but not developed or hosted by Rygen.
- Marketing or experimental prototypes not deployed to production.
AI systems previously excluded enter the AIMS scope when any of the following occur:
- Formal entry into the AI System Development Lifecycle
- Processing of real customer or production data
- Accessibility by clients or external users
- Integration with production systems
- Budget allocation for production deployment
These exclusions will be reviewed quarterly or upon major architectural changes.
Justification and Boundaries
This scope is defined based on:
- External Issues (see 4.1a): AI pressure from market, risk of regulatory shifts, client expectations, climate change impacts and related regulatory developments.
- Internal Issues (see 4.1b): Current architecture, team structures, development workflows, risk profile.
- Stakeholder Expectations (see 4.2): Clients, leadership, compliance, engineering.
The scope prioritizes customer-facing AI functionality and internal automation that can impact security, reliability, client trust, and compliance.
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-01-13 | Field Bradley | Broadened scope statement |
| 1.3 | 2026-01-16 | Field Bradley | Added climate change to external issues per ISO/IAF communique (AI-1230) |