switch to linux
This commit is contained in:
parent
9631d7d41c
commit
72ee692010
@ -1,2 +1,2 @@
|
||||
FCC - fixed charge coverage ratio - looks at cash flow as compared to cash require dto fulfill debt payments
|
||||
FCC - fixed charge coverage ratio - looks at cash flow as compared to cash require dto fulfill debt payments
|
||||
SLR - senior debt leverage ratio - senior debt to ebitda
|
15
bash.md
Normal file
15
bash.md
Normal file
@ -0,0 +1,15 @@
|
||||
|
||||
Update PostgreSQL
|
||||
------------------------------------------------------------------------------------------------------------
|
||||
|
||||
wget -q https://www.postgresql.org/media/keys/ACCC4CF8.asc -O - | sudo apt-key add -
|
||||
|
||||
sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt/ `lsb_release -cs`-pgdg main" >> /etc/apt/sources.list.d/pgdg.list'
|
||||
|
||||
sudo apt-get update
|
||||
|
||||
sudo apt-get install postgres-10
|
||||
|
||||
sudo su - postgres
|
||||
|
||||
psql
|
@ -1,2 +1,2 @@
|
||||
|
||||
|
||||
new business startup on $1000 and 90 days [blog](https://medium.com/the-mission/seth-godin-new-business-5-step-fdb354988c23)
|
@ -1,20 +1,20 @@
|
||||
CREATE TABLE mast.node
|
||||
(
|
||||
id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY
|
||||
,nam text
|
||||
,sch text
|
||||
,doc jsonb
|
||||
|
||||
)
|
||||
|
||||
|
||||
CREATE TABLE acct.accm
|
||||
(
|
||||
id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY
|
||||
,nam text
|
||||
--reference to node ids
|
||||
--should be limited to certain types of nodes, like location, product line, fsline, perhaps an enum?
|
||||
,nodes bigint[]
|
||||
--node attributes pooled here
|
||||
,doc jsonb
|
||||
CREATE TABLE mast.node
|
||||
(
|
||||
id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY
|
||||
,nam text
|
||||
,sch text
|
||||
,doc jsonb
|
||||
|
||||
)
|
||||
|
||||
|
||||
CREATE TABLE acct.accm
|
||||
(
|
||||
id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY
|
||||
,nam text
|
||||
--reference to node ids
|
||||
--should be limited to certain types of nodes, like location, product line, fsline, perhaps an enum?
|
||||
,nodes bigint[]
|
||||
--node attributes pooled here
|
||||
,doc jsonb
|
||||
)
|
@ -1,30 +1,30 @@
|
||||
Version 10 Features
|
||||
===================
|
||||
|
||||
Auto Logging [blog](http://databasedoings.blogspot.com/2017/07/cool-stuff-in-postgresql-10-auto-logging.html)
|
||||
|
||||
Transition Tables [blog](http://databasedoings.blogspot.com/2017/07/cool-stuff-in-postgresql-10-transition.html)
|
||||
|
||||
Correlated Columns Query Plan [blog](https://blog.2ndquadrant.com/pg-phriday-crazy-correlated-column-crusade/)
|
||||
|
||||
Native Partitioning
|
||||
|
||||
Logical Replication
|
||||
|
||||
Add a version of jsonb's delete operator that takes an array of keys to delete (Magnus Hagander)
|
||||
|
||||
Make json_populate_record() and related functions process JSON arrays and objects recursively (Nikita Glukhov)
|
||||
|
||||
Identity Columns [blog](https://blog.2ndquadrant.com/postgresql-10-identity-columns/)
|
||||
|
||||
Add view pg_hba_file_rules to display the contents of pg_hba.conf (Haribabu Kommi)
|
||||
|
||||
Add XMLTABLE function that converts XML-formatted data into a row set (Pavel Stehule, Álvaro Herrera)
|
||||
|
||||
|
||||
Security
|
||||
===================
|
||||
|
||||
LDAP & Active Directory [blog](https://www.openscg.com/2017/07/setting-up-ldap-with-active-directory-in-postgresql/)
|
||||
|
||||
Version 10 Features
|
||||
===================
|
||||
|
||||
Auto Logging [blog](http://databasedoings.blogspot.com/2017/07/cool-stuff-in-postgresql-10-auto-logging.html)
|
||||
|
||||
Transition Tables [blog](http://databasedoings.blogspot.com/2017/07/cool-stuff-in-postgresql-10-transition.html)
|
||||
|
||||
Correlated Columns Query Plan [blog](https://blog.2ndquadrant.com/pg-phriday-crazy-correlated-column-crusade/)
|
||||
|
||||
Native Partitioning
|
||||
|
||||
Logical Replication
|
||||
|
||||
Add a version of jsonb's delete operator that takes an array of keys to delete (Magnus Hagander)
|
||||
|
||||
Make json_populate_record() and related functions process JSON arrays and objects recursively (Nikita Glukhov)
|
||||
|
||||
Identity Columns [blog](https://blog.2ndquadrant.com/postgresql-10-identity-columns/)
|
||||
|
||||
Add view pg_hba_file_rules to display the contents of pg_hba.conf (Haribabu Kommi)
|
||||
|
||||
Add XMLTABLE function that converts XML-formatted data into a row set (Pavel Stehule, Álvaro Herrera)
|
||||
|
||||
|
||||
Security
|
||||
===================
|
||||
|
||||
LDAP & Active Directory [blog](https://www.openscg.com/2017/07/setting-up-ldap-with-active-directory-in-postgresql/)
|
||||
|
||||
Add SCRAM-SHA-256 support for password negotiation and storage (Michael Paquier, Heikki Linnakangas)
|
@ -1,21 +1,21 @@
|
||||
|
||||
Only applies to items that exist in both sets of data
|
||||
|
||||
**Change in Price**
|
||||
|
||||
( P₂ - P₁ ) Q₂
|
||||
|
||||
**Change in Quantity**
|
||||
|
||||
( Q₂ - Q₁ ) P₁
|
||||
|
||||
_To further break out change in quantity_
|
||||
|
||||
|
||||
Change in Quantity - _Volume Related_
|
||||
|
||||
Q₂ ( Q₁ / Σ ( Q₁ ) ) - Q₁
|
||||
|
||||
Change in Quantity - _Mix Related_
|
||||
|
||||
|
||||
Only applies to items that exist in both sets of data
|
||||
|
||||
**Change in Price**
|
||||
|
||||
( P₂ - P₁ ) Q₂
|
||||
|
||||
**Change in Quantity**
|
||||
|
||||
( Q₂ - Q₁ ) P₁
|
||||
|
||||
_To further break out change in quantity_
|
||||
|
||||
|
||||
Change in Quantity - _Volume Related_
|
||||
|
||||
Q₂ ( Q₁ / Σ ( Q₁ ) ) - Q₁
|
||||
|
||||
Change in Quantity - _Mix Related_
|
||||
|
||||
Q₂ - Q₂ ( Q₁ / Σ ( Q₁ ) )
|
@ -1,55 +1,55 @@
|
||||
Logic to setup production plan, inventory balances, purchases, and shipments
|
||||
|
||||
Starting point
|
||||
- known balances STKB
|
||||
- known available BOLH - not posted
|
||||
- known prod schedule SOFT
|
||||
- known shipments Sales Forecast
|
||||
- forecasted orders Sales Forecast
|
||||
- machines that a part can run on ??
|
||||
- actual run-time performance Alternates
|
||||
- actual BOM performance Alternates
|
||||
- actual scrap performance Alternates
|
||||
- available machine time ??
|
||||
|
||||
Populate
|
||||
- forecasted prod schedule
|
||||
- forecasted on-hand (via forecast perpetual transactions)
|
||||
- forecasted available (via forecast transactions)
|
||||
- forecasted purchases
|
||||
|
||||
Iterate through each calendar day
|
||||
1. materialize forecasted purchases
|
||||
1. update on-hand & available
|
||||
2. materialize production
|
||||
1. update on-hand & available
|
||||
3. materialize transfers
|
||||
1. update on-hand & available
|
||||
3. materialize shipments
|
||||
1. update on-hand & available
|
||||
4. process forecasted order submissions
|
||||
1. check for inventory available
|
||||
1. Yes
|
||||
1. mark unavailable
|
||||
2. schedule shipment for request date
|
||||
2. No or partial
|
||||
1. mark unavailable any partial
|
||||
2. schedule on next open slot regardless of request date (each part should be mapped to certain set of machines)
|
||||
1. raw materials available
|
||||
1. Yes
|
||||
1. mark unavailable (at begin prod date?)
|
||||
2. No
|
||||
1. mark unavailable any partial (at begin prod date?)
|
||||
2. schedule a purchase net of lead time
|
||||
2. sub-components available?
|
||||
1. Yes
|
||||
1. mark unavialable (at begin prod date?)
|
||||
2. No
|
||||
1. (return to 4.1.2.2)
|
||||
3. schedule transfer of production after completion if necessary
|
||||
3. schedule shipment for request date, or production date if past request date
|
||||
|
||||
|
||||
snap-shot STKB
|
||||
snap-shot BOLH
|
||||
Logic to setup production plan, inventory balances, purchases, and shipments
|
||||
|
||||
Starting point
|
||||
- known balances STKB
|
||||
- known available BOLH - not posted
|
||||
- known prod schedule SOFT
|
||||
- known shipments Sales Forecast
|
||||
- forecasted orders Sales Forecast
|
||||
- machines that a part can run on ??
|
||||
- actual run-time performance Alternates
|
||||
- actual BOM performance Alternates
|
||||
- actual scrap performance Alternates
|
||||
- available machine time ??
|
||||
|
||||
Populate
|
||||
- forecasted prod schedule
|
||||
- forecasted on-hand (via forecast perpetual transactions)
|
||||
- forecasted available (via forecast transactions)
|
||||
- forecasted purchases
|
||||
|
||||
Iterate through each calendar day
|
||||
1. materialize forecasted purchases
|
||||
1. update on-hand & available
|
||||
2. materialize production
|
||||
1. update on-hand & available
|
||||
3. materialize transfers
|
||||
1. update on-hand & available
|
||||
3. materialize shipments
|
||||
1. update on-hand & available
|
||||
4. process forecasted order submissions
|
||||
1. check for inventory available
|
||||
1. Yes
|
||||
1. mark unavailable
|
||||
2. schedule shipment for request date
|
||||
2. No or partial
|
||||
1. mark unavailable any partial
|
||||
2. schedule on next open slot regardless of request date (each part should be mapped to certain set of machines)
|
||||
1. raw materials available
|
||||
1. Yes
|
||||
1. mark unavailable (at begin prod date?)
|
||||
2. No
|
||||
1. mark unavailable any partial (at begin prod date?)
|
||||
2. schedule a purchase net of lead time
|
||||
2. sub-components available?
|
||||
1. Yes
|
||||
1. mark unavialable (at begin prod date?)
|
||||
2. No
|
||||
1. (return to 4.1.2.2)
|
||||
3. schedule transfer of production after completion if necessary
|
||||
3. schedule shipment for request date, or production date if past request date
|
||||
|
||||
|
||||
snap-shot STKB
|
||||
snap-shot BOLH
|
||||
snap-shot SOFT
|
@ -1,47 +1,51 @@
|
||||
A method to planning sales
|
||||
----------------------------
|
||||
|
||||
## Summary
|
||||
|
||||
1. copy history
|
||||
|
||||
1. start with open orders
|
||||
2. add orders as placed in past
|
||||
1. true-up to current run rate
|
||||
1. normalize price for current pricing
|
||||
1. will need to idenitfy blocks in the base period that best represent pricing efforts
|
||||
2. scale prior periods to match final pricing
|
||||
2. exclude expired products/customers
|
||||
3. scale new developments to reflect full-year (new products customers)
|
||||
4. update cost to current
|
||||
5. request date attainment performance
|
||||
3. walk prior period sales to new baseline sales as change in run-rate
|
||||
|
||||
2. build in changes to current run-rate
|
||||
|
||||
1. volume changes
|
||||
2. pricing changes
|
||||
3. new products (must be defined in future at a mininum)
|
||||
4. future cost changes
|
||||
5. request date attainment
|
||||
|
||||
|
||||
|
||||
| timeline | day | running days | responsible |
|
||||
| -------------------------------------------- | --- | ------------ | ----------- |
|
||||
| **_establish run-rate sales_** | | | |
|
||||
| copy history | 1 | 1 | executor |
|
||||
| identify pricing windows | 1 | 2 | sales team |
|
||||
| scale windows to match final | 1 | 3 | executor |
|
||||
| identify expired products/customers | 3 | 6 | sales team |
|
||||
| eliminate expired volume | 1 | 7 | executor |
|
||||
| identify new products/customers | 3 | 10 | sales team |
|
||||
| scale new to full year volume | 1 | 11 | executor |
|
||||
| **_load new plans_** | | | |
|
||||
| layer in planned changes not yet implemented | | | |
|
||||
| identify changes to existing volume | 3 | 14 | sales team |
|
||||
| load changes | 1 | 15 | executor |
|
||||
| identify changes in price | 3 | 18 | sales team |
|
||||
| load changes | 1 | 19 | executor |
|
||||
| identify new products | 3 | 22 | sales team |
|
||||
| load new | 1 | 23 | executor |
|
||||
A method to planning sales
|
||||
----------------------------
|
||||
|
||||
## Summary
|
||||
|
||||
1. copy history
|
||||
|
||||
1. start with open orders
|
||||
2. add orders as placed in past
|
||||
1. true-up to current run rate
|
||||
1. normalize price for current pricing
|
||||
1. will need to idenitfy blocks in the base period that best represent pricing efforts
|
||||
2. scale prior periods to match final pricing
|
||||
2. exclude expired products/customers
|
||||
3. scale new developments to reflect full-year (new products customers)
|
||||
4. update cost to current
|
||||
5. request date attainment performance
|
||||
3. walk prior period sales to new baseline sales as change in run-rate
|
||||
|
||||
2. build in changes to current run-rate
|
||||
|
||||
1. volume changes
|
||||
2. pricing changes
|
||||
3. new products (must be defined in future at a mininum)
|
||||
4. future cost changes
|
||||
5. request date attainment
|
||||
|
||||
|
||||
|
||||
| timeline | day | running days | responsible |
|
||||
| -------------------------------------------- | --- | ------------ | ----------- |
|
||||
| **_establish run-rate sales_** | | | |
|
||||
| copy history | 1 | 1 | executor |
|
||||
| identify pricing windows | 1 | 2 | sales team |
|
||||
| scale windows to match final | 1 | 3 | executor |
|
||||
| identify expired products/customers | 3 | 6 | sales team |
|
||||
| eliminate expired volume | 1 | 7 | executor |
|
||||
| identify new products/customers | 3 | 10 | sales team |
|
||||
| scale new to full year volume | 1 | 11 | executor |
|
||||
| **_load new plans_** | | | |
|
||||
| layer in planned changes not yet implemented | | | |
|
||||
| identify changes to existing volume | 3 | 14 | sales team |
|
||||
| load changes | 1 | 15 | executor |
|
||||
| identify changes in price | 3 | 18 | sales team |
|
||||
| load changes | 1 | 19 | executor |
|
||||
| identify new products | 3 | 22 | sales team |
|
||||
| load new | 1 | 23 | executor |
|
||||
|
||||
|
||||
|
||||
Table Layout
|
||||
|
Loading…
Reference in New Issue
Block a user