AgriRetail Reference Architecture - AMS 2025/26

A comprehensive reference architecture specification for the AgriRetail Alliance platform, coordinating agricultural supply and demand through automated logistics and information systems. Developed as part of the Architecture and Modeling of Systems (AMS) course at IST.

Project Overview

The AgriRetail Alliance is a collaboration between agricultural producers and retailers seeking a new platform to coordinate the supply and demand of agricultural products. This project develops an Open Domain Reference Architecture Specification through a competitive exploration process, modeling:

• AgriCore - Logical information system
• Transport Unit - Physical system (semi-trailer trucks)
• Collection & Delivery Processes - End-to-end logistics workflows

System Objectives

1. Reliable Coordination - Effectively align supply and demand between producers and retailers
2. Transparent Forecasting & Planning - Anticipate needs and production in a timely manner
3. Order Efficiency - Ensure orders are matched and delivered quickly and reliably
4. Automated Logistics - Minimize human intervention in transport and storage
5. National Coverage - Enable participation of producers and retailers across the country
6. Fair Information Usage - Balance business privacy with traceability and equitable access

Deliverables

Phase 1 (PRJ1)

Focus: Understanding the domain and key processes

1. Assumptions - Explicit and implicit assumptions list
2. Open Questions - Identified ambiguities and omissions
3. High-Level Vision - ArchiMate layered diagram
4. Collection Process - BPMN collaboration diagram

Phase 2 (PRJ2)

Focus: Complete architectural specification

All Phase 1 items (revised) plus:

5. AgriCore Use Cases - UML use case diagram
6. AgriCore Domain Model - UML class diagram
7. Register Order UC - Detailed textual description
8. Register Order Sequence - UML sequence diagram with external interactions
9. Semi-Trailer State Machine - Complete lifecycle STM
10. Transport Unit Use Cases - SysML use case diagram
11. Transport Unit Structure - SysML block definition diagram
12. Transport Unit Internal Structure - SysML internal block diagram

System Architecture

Core Components

AgriCore (Information System)

• Manages all event data (orders, batches, containers, producers, retailers, warehouses, transport units)
• Receives real-time updates from Ministry of Agriculture (product types, certifications)
• Daily planning cycle (20:00) with Planner service
• Coordinates with GesPark (park management) and GesStore (warehouse management)
• Tracks all collection and delivery events

Transport Unit (Physical System)

• Composition: Semi-trailer truck (tractor) + trailer
• Electric tractor with TruckMng application
• Real-time sensor monitoring
• Autonomous navigation using Galileo + Google Maps
• Automated rescue protocol for battery depletion
• Lifecycle states: operational, inoperational, in use, deactivated

External Systems

• Planner - Route planning and order fulfillment optimization
• Ministry of Agriculture - Product types and certification registry
• Google Maps - Route assistance
• Galileo - GPS navigation system
• GesPark - Automated park management
• GesStore - Automated warehouse management

Key Processes

Collection Process

1. AgriCore receives collection plan from Planner
2. Transport Unit assembly at park
3. Container loading onto trailer
4. Multi-producer collection route
5. Warehouse delivery and container unloading
6. Return to designated park
7. Unit disassembly

Delivery Process

1. AgriCore receives delivery plan from Planner
2. Transport Unit assembly at park
3. Warehouse pickup of designated containers
4. Multi-retailer delivery route
5. Empty container return to park
6. Unit disassembly

Modeling Tools & Standards

Tools

• ArchiMate - Enterprise architecture modeling (Archi tool → EA)
• BPMN 2.0 - Business process modeling (Camunda → EA)
• UML 2.5 - Use cases, domain models, sequences, state machines (EA)
• SysML - Physical system modeling (EA)
• Enterprise Architect (EA) - Final modeling tool for Phase 2

Standards & Frameworks

• ArchiMate 3.x - Layered architecture representation
• BPMN 2.0 - Collaboration and process flows
• UML 2.5 - Object-oriented modeling
• SysML 1.6 - Systems engineering

Key Domain Concepts

Stakeholders

• Retailers - Submit orders and demand forecasts; single delivery location
• Producers - Declare production batches and forecasts; multiple production/collection sites
• AgriRetail Alliance - Platform operator
• Ministry of Agriculture - Regulatory authority

Business Rules

• Orders cannot target specific producers but can require certifications
• Producers cannot choose retailers or influence order decisions
• Forecasts, orders, and productions cannot be modified after creation
• Orders confirmed only when all products are in warehouses
• Products never transferred between warehouses
• Each container carries only one batch type
• Batches can be split into sub-batches for transport/fulfillment

Lifecycle Management

• Orders: Registered → Pre-confirmed → Confirmed → Fulfilled/Unfulfilled/Cancelled
• Batches: Declared → Collected → In warehouse → Delivered
• Transport Units: Assembled → In movement → Stopped (loading/unloading/parked) → Disassembled

Reference Architecture Perspective

This project goes beyond modeling a single system - it aims to define a reusable reference architecture applicable to similar coordination platforms across different sectors (industrial logistics, circular economy, healthcare, transportation).

Reusability Principles

• Stable vs. Variable Elements - Clear separation between invariant core and configurable aspects
• Technology Independence - Logical structure maintained across different implementations
• Viewpoint Articulation - Multiple perspectives (business, information, technology, governance)
• Sector Adaptability - Generic patterns applicable to various domains

Inspiration from Industry

Similar reference architectures exist in:

• Industrial IoT (IIRA, RAMI 4.0)
• Enterprise integration (ISA-95)
• Smart cities (FIWARE, OASC/MIMs)
• Telecommunications (TM Forum ODA)
• Automotive (AUTOSAR)
• Healthcare (HL7, openEHR)
• Government (EIF/EIRA, GOV.UK)

Getting Started

Prerequisites

• Enterprise Architect (EA) - Primary modeling tool
• Archi - For initial ArchiMate diagrams (Phase 1)
• Camunda Modeler - For initial BPMN diagrams (Phase 1)

Documentation Standards

• All diagrams must include appropriate legends
• Annotations clarifying view objectives and scope
• Revision notes for updated diagrams in Phase 2
• Explicit confirmation when diagrams are re-examined without changes

Out of Scope

The following aspects are explicitly excluded:

• Payment and billing systems
• Security and cybersecurity
• Long-term strategic planning
• Member lifecycle management
• Equipment failure scenarios
• Expired batch handling
• Internal design of external services (Planner, TruckMng)
• Producer loading failures or retailer delivery rejections

Learning Outcomes

Students will develop competencies in:

• Enterprise architecture modeling (ArchiMate)
• Business process modeling (BPMN)
• Object-oriented analysis and design (UML)
• Systems engineering (SysML)
• Requirements analysis and critical thinking
• Stakeholder communication
• Reference architecture design principles

Excellence Criteria

A solution of excellence demonstrates:

• Vision beyond explicit requirements
• Critical analysis and generalization capacity
• Clear distinction between stable and variable elements
• Explicit viewpoint awareness and articulation
• Evidence of reusability principles
• Technical rigor with communicational clarity

---

"An architecture is only as good as its ability to be understood, reused, and evolved by its community."