Overview

The Operation, Administration, and Maintenance (OAM) domain governs the lifecycle of the platform itself: bringing new tenants and users onboard, managing identities and access, and tracking subscription and billing state. The OAM domain follows the FCAPS model used in telecommunications and IT operations — Fault, Configuration, Accounting, Performance, and Security — adapted to the Arda multi-tenant SaaS context.

Of the five FCAPS areas, three are currently undocumented:

Fault (OAM::FLT) — Failure detection, alerting, and incident management. No use cases documented.
Performance (OAM::PRF) — Throughput, latency, and capacity monitoring. No use cases documented.
Security (OAM::SEC) — Threat detection, audit logging, and policy enforcement. No use cases documented.

The three areas with documented behavior are:

Configuration Behaviors — OAM::CFG: onboarding workflow, phased rollout guidance, and user/tenant display preferences
Identity and Access Management Behaviors — OAM::IAM: user registration, authentication, password management, account profile, company administration, invitations, and customer acquisition channels
Accounting and Cost Behaviors — OAM::ACT: subscription and billing information