Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B backbone
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • backbone
  • backbone
  • Issues
  • #129
Closed
Open
Created Jul 03, 2020 by Juha Kiviluoma@juha_kOwner

Reserve activation duration

Faster reserves are typically required only for a shorter period of time (e.g. 15 minutes). This should be accounted for when providing reserves from storages. We should add reserve_activation_duration to p_groupReserves or p_groupReserves3D and update state constraints.

There could also be a further reactivation requirement: how fast the unit needs to be ready to be activated again for the same purpose. Even though this is a thing in some systems, maybe not worthwhile to be implemented in Backbone unless there is an explicit need.

Edited Aug 31, 2020 by Juha Kiviluoma
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

This system is mainly used for VTT projects and partners in those projects. Default permission does not allow user to create projects / groups. If you are VTT person, please contact Kimmo Ahola for getting permissions.