commit 2e0552bac0267062f2a02d0eb302b88feeb705ee
parent c89c316b7052a6bee3ea25a59695fd9b2fbd2412
Author: Bob Haugen <bob.haugen@gmail.com>
Date: Sat, 3 Aug 2019 17:02:24 -0500
Merge pull request #532 from valueflows/fixes
fixes, cont. - including qty vs time, for further comment
Diffstat:
2 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/docs/introduction/flows.md b/docs/introduction/flows.md
@@ -84,6 +84,29 @@ We have defined a core set of actions, but expect that this will be extended wit
(2) The actions `transfer` and `move` can optionally define a second identified resource on the receiver side.
+### Quantities and Times
+
+Quantities are used for counting, such as:
+* Exchange/transfer
+* Resource increment and decrement
+* Recipes, how much or many goes into and out of a transformation process
+
+Times are used for coordination, such as:
+* Calendar availability
+* Planned timelines
+
+They can be used together for analysis and reporting, such as:
+* Accounting totals (quantity) within accounting period (time)
+
+Quantities can be any needed unit of measure, including counts, volumes, weights, etc. Time can be a duration or an instant. Note that recipes may need to scale both quantities and calendar times when used to create a plan.
+
+Sometimes a quantity is expressed in time-based units, like "I worked 6 hours", or "we used this machine for 8 hours". These flows also will have a related time, like "I worked from 10am to 4pm", or "we used this machine from 8am to 4pm". In these examples, the quantity is used for accounting figures, exchange, recipes. The time is used to schedule and coordinate the work or machine usage.
+
+Sometimes a situation may call for a "compound quantity", like "Number-per-Year".
+
+Times can have different levels of exactness based on the need. For example a commitment might specify that a task should be done by a certain date, but it doesn't matter when it is done before that date.
+
+
### Examples
[import, lang:"yaml"](../../examples/fulfill-satisfy.yaml)
diff --git a/release-doc-in-process/ValueFlowsUML.png b/release-doc-in-process/ValueFlowsUML.png
Binary files differ.
