SoloDB Documentation version 0.1-DEV Help

Rooms

Overview

Rooms in SoloDB represent physical spaces within buildings that can be managed and organized. They are a key component in the hierarchical structure of space management, positioned between buildings and zone groups. Rooms serve as the primary unit for organizing physical spaces, managing access control, and tracking equipment.

Hierarchical Position

Rooms exist within the following hierarchical structure:

Site └── Building └── Room └── Zone Group ├── Zone └── Location

Room Properties

Rooms have the following properties:

  • Name: Descriptive name of the room

  • Code: Unique identifier for the room

  • Department: Department responsible for the room

  • Purpose: The intended use of the room

  • Tags: Keywords for categorizing the room

  • Opening Hours: Regular hours when the room is accessible

  • After Office Hours: Access information for after regular hours

  • Description: Detailed description of the room

  • Phone: Contact phone number for the room

  • Location Details: Additional details about the room's location

  • Status: Active, Inactive, or Deleted

  • Training Description: Information about required training for room access

Room Relationships

Rooms have relationships with various entities in the system:

  • A room belongs to a building

  • A room can have a label

  • A room can have multiple floor plans

  • A room can have multiple links

  • A room can have multiple zone groups

  • A room can have multiple roles

  • A room can have multiple users

  • A room can have multiple projects

  • A room can have multiple programs

  • A room can have multiple documents

  • A room can have multiple requests

  • A room can have multiple equipment items

  • A room can be associated with multiple equipment properties

  • A room can be associated with multiple modules

Room Roles

Rooms can have designated responsible users with specific roles:

  • Roles can be defined for rooms (e.g., "Room responsible", "Backup responsible", "Hardware responsible")

  • Each role is a responsible user and can be active in the training approval flow

  • Roles can be created and managed through the admin interface

  • Users with roles can be part of the approval flow for training requests

Training and Access Control

Rooms implement a training and access control system:

Training Settings

  • Training can be set as possible or not possible for a room

  • A training description can be provided to give users more information

  • Different reservation options can be configured:

    1. No reservations possible

    2. Reservations possible for all users

    3. Reservations only possible for trained users

    4. Reservations possible for trained users and users in training

Training Statuses

Users can have different training statuses for a room:

  • Active: User is fully trained and has access

  • Mentor: User is an experienced user and can act as mentor for other users

  • In training: Training request has been approved but training not completed

  • Waiting for training: Request approved but training not started

  • Inactive: User is not trained anymore

Training Request Process

  1. User requests training through a form providing:

    • Reason for training

    • Necessary equipment

    • Materials used in room

    • Frequency of use

  2. Approval flow starts where responsible users must approve

  3. Only one user per role is needed to complete the request

  4. Users and responsible users receive email updates

  5. Approved requests are archived

Mentor System

For larger rooms, a mentor system can be implemented:

  • Experienced users can act as mentors for other users

  • The mentor system is automatically enabled if at least one trained user is set as a Mentor

  • New users must select a mentor when requesting training

  • The mentor must approve the mentorship before the training request can be approved

Zone Organization

Rooms can be organized into smaller functional units:

Zone Groups

  • A zone group is a collection of zones grouped together for a specific purpose

  • Zone groups have a limited capacity of concurrent users

  • SoloDB can track the current number of users via the zone reservation system

  • Equipment properties can be linked to a zone group, affecting all equipment in that group

Zones

  • Zones are specific areas within a zone group that can contain equipment

  • Equipment stored in a zone inherits the properties of the zone group

Common Use Cases

Rooms in SoloDB are used for:

  1. Space Management: Organizing physical spaces within buildings

  2. Equipment Tracking: Managing where equipment is stored or installed

  3. Access Control: Managing who can access specific rooms through training requirements

  4. Reservation Management: Controlling how rooms and zones can be reserved

  5. Project Organization: Associating projects and programs with specific rooms

Integration with Other Modules

Rooms integrate with other modules in SoloDB:

  • Equipment Module: For tracking equipment within rooms, zones, and locations

  • User Module: For managing access and training

  • Project Module: For associating projects with rooms

  • Document Module: For storing documents related to rooms

12 June 2025