update readme
This commit is contained in:
parent
3393136148
commit
c5b9d39b5a
61
README.md
61
README.md
@ -1,54 +1,13 @@
|
|||||||
Special concepts
|
## Setup
|
||||||
* relationships betwen dates (order, request, ship) and apply that mix to a new month
|
|
||||||
* apply a base mix of promo codes and terms codes to a new month of forecast where there is no existing baseline to pull from
|
|
||||||
* effects of building baselines off of original, or all changes so far
|
|
||||||
* pricing and units
|
|
||||||
|
|
||||||
Slowness Options
|
* git clone (to //opt for verbatim use of the .service file)
|
||||||
* move json to a separate table and the change can be marked with a sequence
|
* npm install
|
||||||
* have the data actually be a query from the database
|
* create certs (`./create_certs.sh`)
|
||||||
* reduce number of columns in fc_pool
|
* populate .env from template for database creds and listening port for API, and working directory
|
||||||
|
* copy .service file to //etc/systemd/system/ (adjust user/working direct if needed)
|
||||||
|
* `sudo systemctl enable forecast_api.service`
|
||||||
|
|
||||||
Discussion
|
## Initial Forecast
|
||||||
* special look at Mar-Apr sales since it is being copied from plan or older data
|
|
||||||
- [ ] at the end of March, we will swap out the budget from March with actuals and re-forecast
|
|
||||||
- [ ] need to think through how to overlay actuals into the budget
|
|
||||||
* last price paid snap - preload
|
|
||||||
- [ ] dont do this
|
|
||||||
* FX - currently nothing loaded
|
|
||||||
- [ ] we'll pick one (see Bruno)
|
|
||||||
* cost - snap to current cost
|
|
||||||
- [ ] snap to current
|
|
||||||
* need to be able to reload the forecast as we lock in new months of sales data - replay changes over top?
|
|
||||||
* item 1
|
|
||||||
* refresh new part list
|
|
||||||
* add comments on monthly
|
|
||||||
* add a tag that is separate from the comment?
|
|
||||||
* need to test extrapolating osm_pool into osmp_dev
|
|
||||||
|
|
||||||
Review
|
* all SQL depends on unchanged core sales matrix table schema
|
||||||
* continuous update with actuals
|
* build/build_baseline.sql
|
||||||
* next years sales is going to change everyday as new things happen with open orders
|
|
||||||
* need to be populating shipping season instead of leaving null
|
|
||||||
* need to do with past-due's -> when do they ship?
|
|
||||||
* snapshot several years of history into the forecast so there is no need to bring in actuals
|
|
||||||
* going to have to rebuild the forecast when actuals change
|
|
||||||
|
|
||||||
CI
|
|
||||||
* snapshot pool
|
|
||||||
* adjust 2021 orders
|
|
||||||
* integrate with 2020 open to get to 2021 sales (osm_stack)
|
|
||||||
* show 2021 forecasted order as forecast
|
|
||||||
* show 2021 forecasted sales (need to update ship season so it is not null)
|
|
||||||
|
|
||||||
Walk Issues
|
|
||||||
* canceled orders
|
|
||||||
* changed orders
|
|
||||||
* short ships
|
|
||||||
* exchange rates
|
|
||||||
|
|
||||||
Things to Demo
|
|
||||||
* product swap out
|
|
||||||
* pivot re-org
|
|
||||||
* don't use filters
|
|
||||||
* assumes all changes target USD
|
|
||||||
|
Loading…
Reference in New Issue
Block a user