commit 8b74d34a08083ad0ce0d6cce83205b69955b1aae
parent 709eec56aa6168906b390f3262e063404243bdd8
Author: Bob Haugen <bob.haugen@gmail.com>
Date: Sun, 4 Aug 2019 17:55:33 -0500
Merge pull request #536 from valueflows/reverse-pics
fix reversed pics
Diffstat:
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/introduction/estimates.md b/docs/introduction/estimates.md
@@ -26,4 +26,4 @@ Scenarios can be refinements of other scenarios. For example, a group might do
If other requirements arise, we are happy to add connections as needed to the vocabulary.
-
+
diff --git a/docs/introduction/plan.md b/docs/introduction/plan.md
@@ -33,4 +33,4 @@ When processes are "nested", it is not random, nor based on a taxonomy. It is ba
Plans can be generated from a recipe by scaling the recipe according to the demanded quantity of the end outputs. This is called a "demand explosion". The generation might take into account current inventories, batch sizes, etc., so it is not necessarily a "pure" reflection of the recipe. In addition, often plans are tweaked after generation from a recipe, depending on how firm and exact the recipe is. A manufacturing recipe might be more exact than a recipe for a more general business process. For these reasons, a plans is decoupled from the recipe that generated it in the vocabulary. It maintains only the references to the resource and process specifications that were supplied from the recipe.
-
+
