CWR – Framework Reading Sample EN

CWR – Framework Reading Sample EN
My book about business improvement is available in english, however, the implementation is not language-dependent, and it can be used also in privat environments.
My CWR – Framework is a flexible concept that can be adapted to any environment and all needs. I designed it for effectiveness and cost savings.
Remark: At the time of the first publication in 2014 via my website at the time, there were no copies, since then copies have been published again and again, but they neither reflect the meaning of my concept nor can reach the milestones described in my workflow.

Pillars in the CWR – Framework
Even if we are talking about the weather here, the collection in the back-end can be compared with a Marketplace.
CWR-Framework Marketplace. Here everything meets, here everything comes together what should be output at the end on a dashboard(s). This is just like how goods are carried together on a physical marketplace in order to deliver and sell them to the customer. Only here, the customer is the one who wants to see the data on a dashboard, take the goods like it is or change it.
Thus, one of the important things in the ›what’s happened behind the scene‹ of the dashboard(s). The dashboard(s) we generate from it can be compared to the store and the final presentation on the marketplace.

This is how the »w-e-a-t-h-e-r« result can look like after the assignment to the measurement over the AWS:
On the store of our marketplace where everything comes together, needs to package, labeling. Here everything has to be correct before the sale.

Validation
The CWR-Framework haven’t not only one important data entry point. All the core sheets are important to calculate, collect and to show results at the end on our generated dashboards.
The validation data in this table for our basic structure of Information. It builds the basis of the attributes you need it the tables and calculation dependencies.

AWS
The Important sheet to measure. What we want to measure?
Our entries, tasks, points, sections etc., and at the end our business or something else. The AWS are the legs of our business w-e-a-t-h-e-r. If there is climate pollution and poorly treated nature (inside the business) etc., this will be reflected in the CWR w-e-a-t-h-e-r. Here the factors are only.
The calculation of the weather itself. The numbers we want or need, to map on the dashboard(s) at the end of the calculations.

Budget (sheet)
Here we do all the calculation, we want and need, for the coins. The money, bugs or however it must be called.

An important factor in the entire business and of course also in the private sector to see how much we have already spent, and how much we probably still need to spend to achieve our goals or save something.

FQSRSSR (sheet)
This is the Faults, QSR and SSR calculation pivot table.

Proof (Weather-sheet)
The cross-checks to check everything against each other. Good to be able to compare data in conjunction with other data.

Explanation of additional Sheets
Everything that everyone wants or needs can be recorded here. Starting with addresses to special agreements about the business, internal processes, and security regulations.
External and internal services. Security related pieces and business dependent main procedures etc.
The analysis of the business is the core before anything else. After the first important step it can be shown and should be shown what is needed.
There may be certain rules that a company has in place with regard to data protection, data storage, etc. must be noted. Special workflows are also conceivable in which only a few employees need to be specially trained. In general, all processes can be incorporated into the concept.
To emphasize it again: The main focus from the CWR-Framework is on cost savings and simplicity!

With simplified workflows like my CWR framework, millions of dollars can be saved that can be used to grow the business. The industry likes to sell concepts that do not benefit the person who executes them, but rather the inventors. Complicated processes often stand in the way of an increase in the quality of products, which is neither good for the business nor for the customer.