Product Areas
The Arda platform organizes its capabilities into three product areas. Each area groups related capabilities that share a common operational purpose and user audience. Together they cover the full scope of what Arda delivers — from foundational platform services through shop-floor material flow to enterprise procurement and supply chain.
The table below maps each product area to the functional domains that realize it. Domains marked (planned) have no active use cases yet.
Product Area Map
Section titled “Product Area Map”Core Platform Capabilities
Section titled “Core Platform Capabilities”Foundational services that every user and every domain depends on: identity, access control, system administration, and the cross-cutting UX contract.
Administration and Configuration
Section titled “Administration and Configuration”Tenant and user lifecycle, subscription management, self-service onboarding, print template configuration, and business-rule management.
- Functional domain:
OAM— 21 use cases across identity, access, and configuration - Personas: Alan (Account Admin), Owen (Business Principal)
User Experience
Section titled “User Experience”Responsive web interface with advanced data grids, type-ahead lookups, inline editing, bulk operations (CSV import/export), and a unified entity lifecycle (browse → create → edit → publish → archive).
- Functional domains:
GEN— 16 use cases defining the cross-cutting UX contract;APP— dashboard and navigation - Key patterns: Entity Data Authority, List Views, Entity Media
Security and Compliance
Section titled “Security and Compliance”JWT authentication with AWS Cognito, SSO, role-based access control (RBAC), attribute-based access control (ABAC via Cedar policies), and audit trails with bitemporal history.
- Functional domain:
OAM(identity and access area) - Architecture: See Cognito Service, Realms and Scopes, Cedar Authorization
Platform Architecture
Section titled “Platform Architecture”Modular Kotlin/Ktor backend with the Data Authority pattern, bitemporal persistence, and a Query DSL for filtering and pagination. AWS-hosted with Infrastructure as Code (CDK).
- Architecture: See Design Pattern Index, Implementation Patterns
Manufacturing and Material Flow Management
Section titled “Manufacturing and Material Flow Management”Domain capabilities that manage the physical and informational flow of materials through manufacturing and logistics. This is the core of Arda’s Kanban-driven pull system.
Kanban and Pull System Control
Section titled “Kanban and Pull System Control”Digital Kanban cards as the primary pull signal for material replenishment. Cards carry state (Available → Requesting → Ordered → Received), trigger procurement signals, and integrate with QR scanning for shop-floor interaction.
- Functional domain:
RES— 9 use cases for kanban cards and facilities - Personas: Sam (Shop Floor Worker), Irene (Inventory Manager)
- Publications: Card States, Scanning Cards, Kanban Discipline
Inventory and Reference Data
Section titled “Inventory and Reference Data”Item master records, supplier/affiliate records, facility definitions, and the Edit-Draft-Publish lifecycle for all reference data. Supports bulk CSV import/export and item-supply pricing per supplier.
- Functional domain:
REF— 30 use cases across items, suppliers, and business affiliates - Personas: Irene (Inventory Manager)
- Publications: Adding Items, Item Types and Categories, CSV Import
Production and Shop Floor (planned)
Section titled “Production and Shop Floor (planned)”Work order management, production process modeling, shop floor data collection, and labor tracking. Future domains OPS and WFI will cover manufacturing execution and cross-domain workflow choreography.
- Vision: See Vision — Functional for the target capability set including production scheduling, quality management, and asset maintenance.
Business and Supply Chain Operations
Section titled “Business and Supply Chain Operations”Capabilities that manage the broader business context: demand-driven procurement, supplier collaboration, order fulfillment, and the connection between shop-floor consumption and external supply.
Procurement and Supplier Collaboration
Section titled “Procurement and Supplier Collaboration”Full purchase order lifecycle — from demand queue through order creation, submission, receiving, and close. Orders can be created from kanban demand, item lists, or manually. Ten-state lifecycle with submit, amend, receive, and cancel workflows.
- Functional domain:
PRO— 26 use cases across order queue, purchase orders, receiving, and end-to-end flows - Personas: David (Purchasing Manager), Keisha (Receiving Clerk)
- Feature: Purchase Order Feature
- Implementation: Order Lifecycle
Shop Access and Printing
Section titled “Shop Access and Printing”PDF rendering for kanban cards, item labels, and purchase orders. QR code generation for card scanning. Printer integration for shop-floor label and card production.
- Functional domain:
SAC— PDF generation triggered by other domains - Publications: Printing in Arda, Printer Setup
Order Fulfillment (planned)
Section titled “Order Fulfillment (planned)”Demand order ingestion, picking, packing, and shipping. Future domain FUL will cover warehouse fulfillment operations.
- Vision: See Vision — Functional for the target capability set including available-to-promise, waveless fulfillment, and multi-site operations.
Navigation
Section titled “Navigation”| Section | What you’ll find |
|---|---|
| Markets and Value | Market segments and value proposition |
| Personas | The six user personas and their operational goals |
| Features | High-level capability descriptions |
| Use Cases | Detailed behavioral specifications by functional domain |
| Cross-Cutting | Patterns that span multiple domains |
| Publications | User-facing guides and how-tos |
| Offerings | Releases and packaging |
Copyright: © Arda Systems 2025-2026, All rights reserved