Skip to content

Planning.md

Latest commit

 

History

History
72 lines (51 loc) · 4.39 KB

Planning.md

File metadata and controls

72 lines (51 loc) · 4.39 KB

DRAFT !!!

Do not use this for any development !!!

planning-screenshot

Pieces of code:

  • CRUD ProcessSpecifications
    • Add image to ProcessSpecification in the backend
    • List and modal create/update/delete ProcessSpecification, under config menu
  • CRUD recipes (we are thinking to hard code these to start)
    • Recipes are not in hREA I think, need to be added from scratch on backend
    • Design a UI that will work for one-process recipes; but some people will need multi-process recipes
    • Include stage
  • Plan from recipe (works for mfg/assembly and workflow patterns) >> logic in zome?
    • Create Plan with Processes/Intents, demand-driven, using requests as independent demand, "squashing" or "expanding" as needed
      • Choose all the independent demand intents (all the yarn requests)
      • Should we put something in the recipe to say intent or commitment created? and create what it says?
    • Add minimumQuantity to Intent in hREA and to Offer UIs
    • We'll need delete Plan fairly soon, so they can experiment, and fine tune the recipes.
    • Do we need anything more? Or can it figure out all the correct order?
  • Planning page display (offers, requests, plan columns with plan)
    • Visually flag issues (not enough or too much of something) >> logic on client?
  • (Re)Calculate supply-driven quantities, display on page >> logic in client? (is there a way to make this modular for others?)
  • (Re)Calculate demand-driven quantities, display on page >> lobic in client?
  • User can play with the numbers, create/edit intent quantities separately from the calculated ones (should we show payments/costs?)
  • Lock in plan (create a plan with actual commitments, is this one at a time, or the whole thing, or both? > probably best to allow one at a time; include payment commitment and agreement)
  • Notify suppliers of orders (send to them by email? list?)

Then, after the plan is done, it can be used for actual operations:

  • Enter actual economic events against the commitments
  • List of economic events (start of the accounting....)

Followups to morning discussion:

Lynn suggests recipe for scouring, which then is connected via outputs-of-scouring to inputs of other recipe flows. So requests for various yarn mixtures could use recipes for spinning that accept inputs of different scouring outputs. And designs for knitting could use outputs of spinning processes. So could be different recipes per stage that feed off outputs of recipes for other stages. Knitting recipes would include recipes for previous stages by identifying which recipe they want. A series of such inclusions could constitute a longer recipe. The longer recipe could be used by planFromRecipe for a knitted product.

Does that all make sense?

Recipe thoughts:

Stashing the visual here (first version for discussion): cfn-recipes

Tentatively thinking this: cfn-recipes-use

moving this from the other file

Trying to create pseudocode by mining the Django code.

Main code components:

Spelunking

In the template: <input type="submit" name="create-order" id="createOrder" value="{% trans 'Create plan from recipe' %}" In the view:

Lynn Spelunking