Platform Architecture | Oryon Help Center

Purpose

This article provides a high-level overview of the UNEEVO platform architecture, explaining how the different functional modules interact to support complete business processes.

Understanding the platform architecture helps users identify where information is created, how it flows across the system, and how different modules collaborate to deliver an integrated business solution.

This article focuses on the conceptual organisation of UNEEVO rather than on individual features or screens.

Overview

UNEEVO is built as an integrated platform composed of specialised functional modules.

Each module is responsible for managing a specific business domain while sharing information with the rest of the platform through common business entities and standardized processes.

Instead of operating independently, modules collaborate to support complete business workflows that span multiple business areas.

For example, a commercial opportunity managed by the Sales team may eventually become a Project, require Resource allocation, generate Timesheets and ultimately produce Customer Billings.

Uneevo Architecture

At a high level, UNEEVO can be represented as follows:

Uneevo Platform

Although each module specialises in a different business area, they all contribute to a common business ecosystem.

Platform Layers

The UNEEVO platform can be understood as five logical layers.

1. Foundation Layer

The Foundation Layer contains the global configurations shared across the platform.

Typical examples include:

Companies
Business Units
Currencies
Fiscal Years
Tax Configuration
Users
Roles
Permissions
General Parameters

These configurations are typically performed during the initial implementation and are reused by all functional modules.

2. Master Data Layer

This layer contains the core business entities that are shared across multiple modules.

Examples include:

Entity	Description
Person	Individual managed throughout the platform
Company	Customer, supplier or internal organisation
Service	Products or services delivered by the organisation
Resource	Person available to perform work
Contract	Commercial or employment agreement

These entities are created once and reused whenever required.

3. Business Modules

Business Modules support the organisation's operational activities.

Each module focuses on a specific business domain.

Module	Primary Responsibility
People Management	Manage employees and organisational information
Sales Management	Manage commercial opportunities and customer relationships
Project Management	Plan and execute customer projects
Resource Management	Allocate people to project activities
Operations Management	Capture operational execution, including timesheets
Reporting & Analysys	Generate Management Information accross Uneevo Modules

Each module may consume information created by previous modules while producing new information for subsequent processes.

4. Business Processes

Business processes connect multiple modules into complete operational workflows.

For example:

Although each step belongs to a different functional area, together they represent a single business process.

5. Reporting & Analysis

Business information generated throughout the platform can be consolidated for reporting and decision-making.

Typical analysis includes:

Sales performance
Resource utilisation
Project profitability
Operational efficiency
Revenue analysis
Financial indicators

Since information originates from multiple modules, reports provide a unified view of organisational performance.

Module Relationships

The following diagram illustrates how the primary business modules interact.

People Management
        │
        ▼
Resource Management
        │
        ▼
Project Management
        │
        ▼
Operations Management
        │
        ▼
Billing Management

Commercial activities follow a complementary flow.

Sales Management
        │
        ▼
Project Management
        │
        ▼
Billing Management

This architecture allows information created in one area to become the input for another without duplication.

Shared Business Principles

Regardless of the module being used, UNEEVO follows several common principles.

Single Source of Truth

Business information should only be created once and reused whenever possible.

Shared Master Data

Core entities such as People, Companies and Services are available throughout the platform.

Modular Design

Each module specialises in a particular business domain while remaining fully integrated with the rest of the platform.

Process Continuity

Business activities naturally progress across multiple modules instead of being confined to a single area.

Configurable Platform

Most platform behaviour is driven by configuration rather than software customisation.

Understanding Module Dependencies

Although modules are independent from a functional perspective, many rely on configurations or data managed elsewhere.

For example:

Module	Typical Dependencies
Sales Management	Companies, Currencies, Tax Configuration
Project Management	Services, Customers, Resources
Resource Management	People, Contracts
Billing Management	Projects, Billing Plans, Tax Configuration

Understanding these dependencies simplifies implementation planning and avoids configuration issues.