Region
A Region represents a geographic area, market, or territory where your organization operates.
Key Fields
- Name: Region name (e.g., "Europe", "North America", "APAC")
- Code: Short identifier code (e.g., "EU", "NA", "APAC")
- Description: Regional characteristics, regulations, or market details
How It Works
graph TB
Region[Region] -->|scopes| Contexts[Contexts]
Region -->|scopes| Systems[Systems]
Region -->|scopes| Processes[Processes]
Purpose
Regions define:
- Geographic deployment areas
- Market territories
- Regulatory boundaries (e.g., GDPR regions)
- Location-specific business scope
Usage Across Views
Regions are referenced in:
Component View
- Contexts: Where does this context operate?
- Enables filtering by geography
System View
- Systems: Where is this system deployed?
- Shows infrastructure and compliance scope
Process View
- Processes: Where does this process run?
- Maps workflows to geographic markets
Integration
- Storage:
korgraph database, type region
- Hierarchy: Flat structure (no parent/child relationships)
- Relationships: Many-to-many with contexts, systems, and processes
Types of Regions
- Geographic Regions: Continents, countries, states, cities
- Market Regions: Sales territories, distribution zones
- Regulatory Regions: Legal/compliance areas (e.g., EU, California)
- Time Zone Regions: Operational scheduling zones
- Cultural Regions: Markets with shared language/culture
Tips
- Use standardized region names for consistency
- Choose meaningful codes (ISO country codes, abbreviations)
- Document regulatory requirements in descriptions
- Define regions early to enable scope filtering
- Regions help track where systems/processes are deployed
- Consider both business and technical perspectives