Module 4: Architecture of Rise-X

Introduction to Rise-X Architecture 🏛️

Rise-X is designed as a multi-party operational platform that unifies workflows, assets, people, and organisations into interconnected ecosystems. Its architecture focuses on enabling transparency, compliance, and efficiency for complex processes involving multiple stakeholders. The purpose of this module is to give you an understanding of how Rise-X is structured so that you can then think about how you could create a solution on Rise-X to meet your use case. If you want to find a use case for yourself, you can go through module 2 and 3 and think about where in your business Rise-X could be valuable.

Key Architectural Components of Rise-X 🧱

A. Workflows

• These represent business process templates, defining structured steps that guide a process from start to completion. They capture transactions with a clear timeframe and typically conclude once the process is completed. For example, a bunker fuel delivery process or an inspection procedure would be managed as a workflow.
• Workflows consist of:
• Steps: High-level grouping of tasks (e.g. “Order Request”)
• Steps are used to define the columns of the kanban view of your work items.
• Tasks: Individual tasks done by one party and a particular time (e.g. “Order Request Details” and “Order Confirmation” would be tasks inside the “Order Request” Step)
• Components: Data entry fields that can capture a wide range of data types (e.g. text, number, date, table, attachments, signature, etc)
• Activities: As tasks are completed activities can be triggered to perform a wide range of functionalities (e.g. update an asset’s value or send data to an external software)

B. Work Items

• These are instances of a workflow, representing a single business transaction in progress. If a workflow is a template, a work item is a real-world execution of that process. For example, if a workflow template defines how to handle an equipment inspection, a work item would be the inspection of a specific piece of equipment at a particular time.

C. Asset Types

• These define master data structures that store long-lived, reusable business information. They act as templates for different categories of assets, such as "Vehicle," "Supplier," or "Contract." Asset types ensure consistency in how structured data is recorded across the platform.

D. Assets

• These are actual instances of asset types, representing master data records that persist beyond a single workflow. Unlike workflows, assets do not have a specific timeframe, they serve as a single source of truth for reference data used across multiple workflows. For example, a specific ship in a fleet or a long-term supplier agreement would be stored as an asset.

E. Ecosystems

• An ecosystem is a collection of workflows, work items, asset types and assets. Permissions can be set per ecosystem so that the platform can be used as a collaborative environment where the right people have access to only the right information and access.

How Rise-X Architectural Components Interconnect 🔗

• Workflows ↔ Workflows: Workflows can trigger other workflows, creating seamless process automation. For example, completing a "Supplier Approval" workflow could automatically start an "Order Fulfilment" workflow.
• Workflows ↔ Assets: Workflows can capture process data and update assets in real time. For instance, a "Carbon Footprint Verification" workflow could update a product asset with new emissions data.
• Assets ↔ Assets: Assets can reference other assets to maintain accurate relationships. A "Shipment" asset might be linked to a "Product" asset to track logistics data.

Example: Supply Chain Compliance 📝

Scenario:

A 3rd party company verifies the sustainability of a supplier’s product as part of the production workflow.

1. Workflow:
• "Product Order to Delivery"
• Tasks:
• Order Request
• Order Confirmation
• Raw Material Sourcing
• Raw Material Certifications
• Product Production Details
• Testing and Compliance
• 3rd Party Sustainability Audit Certification
• Shipment Details
• Order Received
2. Assets:
• “Raw Materials” asset stores details and certifications.
• "Product" asset stores emissions data.
• "Certification" asset tracks audit results.
3. Ecosystem:
• Supplier, Auditor, Freight Forwarder, Shipping Company, and Buyer companies collaborate in a shared ecosystem.
4. Outcome:
• Immutable records prove compliance, reducing fraud and enabling green certifications all while increasing transparency across the production lifecycle of the product.

Key Takeaways 🔑

• Rise-X connects workflows, assets, people, and companies into shared ecosystems, enabling automation, transparency, and compliance.
• Workflows coordinate actions, while assets store critical data, ensuring seamless operations and better decision-making.

Continue Learning 🚶‍♀️‍➡️

• The next module in the Rise-X Academy covers the best practises in structuring a solution on Rise-X, check it out here.