Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Markus Klinik
c2-planning-scheduling-paper
Commits
1a69d3e5
Commit
1a69d3e5
authored
Apr 04, 2019
by
Markus Klinik
Browse files
terminology: capabilities
parent
b7f940af
Changes
1
Hide whitespace changes
Inline
Side-by-side
introduction.tex
View file @
1a69d3e5
...
...
@@ -76,7 +76,14 @@ For simplicity we focus entirely on reusable resources in this paper.
The connection between tasks and resources are made with
\emph
{
capabilities
}
.
Resources have one or more capabilities, and tasks have one or more
\emph
{
capability requirements
}
.
For example, Bob can have the capabilities Operator, Medic, and Commander.
The task Perform rescue can require a Transport and an Operator.
From a technical standpoint, capabilities are just labels that the scheduler uses to match resources and tasks.
Because the scheduler does not care what capabilities actually stand for, they can be used in different ways.
For example, capabilities can represent professions, completed trainings, military ranks, or identify individual resources.
In the scheduling literature capabilities are often called
\emph
{
skills
}
.
We chose not to use this word, because it suggests that resources can only be people.
We want to emphasize that resources can be anything from machines to people to tools, so we chose a more general term.
\todo
{
use consistently
}
We chose to avoid this word because it suggests that resources are people.
We want to emphasize that resources can be anything including machines, people, and tools, so we chose a more general term.
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment