Learn how to use the Optimus step by step. A typical judging workflow:
-
Setup and start
Before the competition begins, choose how you want to run the system based on event size and your infrastructure.
-
Prepare judging environment
Open existing competition or create a new one, configure the core reference data used during the competition.
This defines how performances are evaluated.
-
Teams and participants - define competitors: teams and their members
Enter manually or import from external sources
How to import teams from CSV file
-
Judges - assign judges and configure their roles
Includes console assignment and trainee mode
Configure judges and trainee mode
-
Rounds and draw - define competition flow
Create manually or generate automatically based on discipline and rules
Generate rounds and draw automatically
-
Categories and ranckings - define how results are grouped and published
elements used for evaluation Divepool and discipline-specific data
- Video handling workflows - prepare media for judging based on your workflow:
Video can be added manually, processed automatically, or used as-is depending on the scenario
Learn more about video scenarios
-
Evaluate performances
Start evaluating performances using the judging workflow that fits your setup.
-
Synchronized judging - all judges evaluate performances simultaneously
Coordinated through an Event Judge, ensuring consistent timing, controlled workflow, and predictable scoring
Recommended for official competitions.
Run synchronized judging
-
Sequential judging - one workstation used by multiple judges in turn
Simple setup for small datasets or certification reviews
This mode is suitable for small datasets or certification and training reviews.
Evaluate on a single workstation
-
Local distributed judging - multiple judges work independently
Shared database and video storage, no strict synchronization required
Judges work independently without strict synchronization.
Handle judging at scale
-
Offline judging - evaluate without network connection
Each workstation runs independently, results are merged later into the main database.
Judging is performed independently, and results are merged after completion.
Designed for field conditions, training sessions, or disconnected environments.
Work in unstable environments
-
Remote judging = evaluate performances from different locations
Extends distributed workflows with asynchronous data exchange
This mode may introduce additional complexity due to external data transfer mechanisms.
Run remote judging
-
Finalize results
After judging is completed, Optimus processes results and generates official competition rankings.
Once marked as official, results become immutableand cannot be modified after approval. It ensures that results are accurate, consistent, and officially approved.
-
Score aggregation - compute final results based on all submitted judges' scores
Results are generated according to configured rules and scoring categories
Official result locking
-
Audit trail - every change is tracked
All modifications are stored in a full history log for traceability
Audit trail and version history
-
Versioning & integrity - each state of results is versioned and linked in a hash chain
Any further changes require a new version of the dataset, preserving full historical integrity.
Conflict detection
-
Publish results
Deliver results to participants, audience, and media.
-
Document output - export results using configure templates
Includes print layouts with customizable structure, logos, fonts, colors, and organizer-specific formatting
Export and configure documents
-
Web publishing - publish results to an online event page
Supports rankings, judges’ scores, and structured competition data
Publish results online
-
Embedded results - integrate results into external websites
Use embedded views to display live or official competition data
Use embedded results
-
Video generation - create replay clips with overlays
Includes scores, rankings, and optional branded intro/outro
Generate video clips