Business Models

These models and simulations have been tagged “Business”.

Related tagsTechnology

  ​Purpose  Enables the different components in the 5 capability model in a visual manner for Enterprise and Business Architecture stakeholders.     5 Capability Model  The 5 capability model has many stock and flow children which each organization will need to model based on their current state.  

​Purpose
Enables the different components in the 5 capability model in a visual manner for Enterprise and Business Architecture stakeholders.  

5 Capability Model
The 5 capability model has many stock and flow children which each organization will need to model based on their current state.  

Semantic

Getting terms to align to the generic objects can be a trying task, unless you simply list the stakeholders "semantic" term below the stakeholder in the presentation layer by order shown in the business process management section above the capability management group.  



The need to spend time doing chargeable work, in balance and/or conflict with the need to spend time doing marketing to ensure a continuing workload into the future.
The need to spend time doing chargeable work, in balance and/or conflict with the need to spend time doing marketing to ensure a continuing workload into the future.
 Harvested fishery with endogenous investment. Ch 9 p340-345 John Morecroft (2007) Strategic Modelling and Business Dynamics

Harvested fishery with endogenous investment. Ch 9 p340-345 John Morecroft (2007) Strategic Modelling and Business Dynamics

Rich Picture se zabývá problémem nízké kvality produktů na trhu
Rich Picture se zabývá problémem nízké kvality produktů na trhu
 Multi-echelon inventory optimization (sounds like a complicated phrase!) looks at the way we are placing the inventory buffers in the supply chain. The traditional practice has been to compute the safety stock looking at the lead times and the standard deviation of the demand at each node of the su
Multi-echelon inventory optimization (sounds like a complicated phrase!) looks at the way we are placing the inventory buffers in the supply chain. The traditional practice has been to compute the safety stock looking at the lead times and the standard deviation of the demand at each node of the supply chain. The so called classical formula computes safety stock at each node as Safety Stock = Z value of the service level* standard deviation * square root (Lead time). Does it sound complicated? It is not. It is only saying, if you know how much of the variability is there from your average, keep some 'x' times of that variability so that you are well covered. It is just the maths in arriving at it that looks a bit daunting. 

While we all computed safety stock with the above formula and maintained it at each node of the supply chain, the recent theory says, you can do better than that when you see the whole chain holistically. 

Let us say your network is plant->stocking point-> Distributor-> Retailer. You can do the above safety stock computation for 95% service level at each of the nodes (classical way of doing it) or compute it holistically. This simulation is to demonstrate how multi-echelon provides better service level & lower inventory.  The network has only one stocking point/one distributor/one retailer and the same demand & variability propagates up the supply chain. For a mean demand of 100 and standard deviation of 30 and a lead time of 1, the stock at each node works out to be 149 units (cycle stock + safety stock) for a 95% service level. You can start with 149 units at each level as per the classical formula and see the product shortage. Then, reduce the safety stock at the stocking point and the distributor levels to see the impact on the service level. If it does not get impacted, it means, you can actually manage with lesser inventory than your classical calculations. 

That's what your multi-echelon inventory optimization calculations do. They reduce the inventory (compared to classical computations) without impacting your service levels. 


 Dynamic system underlying project life cycles From Roberts Edward B The Dynamics of Research and Development p5 Harper & Row NY 1964

Dynamic system underlying project life cycles From Roberts Edward B The Dynamics of Research and Development p5 Harper & Row NY 1964

Process of petrol from a petrol pump being used to fuel vehicles
Process of petrol from a petrol pump being used to fuel vehicles
DRAFT  a small model of a "generic" company.
DRAFT

a small model of a "generic" company.
Learning how to build a systemic dependency - still struggling :)
Learning how to build a systemic dependency - still struggling :)
How the Lean Startup method, developed by Eric Reis, works as a business system.
How the Lean Startup method, developed by Eric Reis, works as a business system.
​The Problem:  What is the true cost of escalation?    Things to measure: How does this impact:1. (MONEY) Cost per incident - what does this cost the business? 2. (TIME) Service Level - how does this impact desired service levels/SLAs? 3. (PEOPLE) Agent utilization - how does this impact backlog? ar
​The Problem: 
What is the true cost of escalation?

Things to measure: How does this impact:1. (MONEY) Cost per incident - what does this cost the business? 2. (TIME) Service Level - how does this impact desired service levels/SLAs? 3. (PEOPLE) Agent utilization - how does this impact backlog? are we overworking engineers? Does this contribute to staff burnout?

We want to know the estimated projected Earnings before tax of a 5 year project. For this we have modeled Sales Growth, Cost of goods sold and Admin. expenses applying sensitivity testing by using probability distributions.
We want to know the estimated projected Earnings before tax of a 5 year project. For this we have modeled Sales Growth, Cost of goods sold and Admin. expenses applying sensitivity testing by using probability distributions.
​The Problem:  What is the true cost of escalating too many Tier 1/Level 1 tickets to Level 2/3 engineers?    Things to measure: How does this impact:1. (MONEY) Cost per incident - what does this cost the business? 2. (TIME) Service Level - how does this impact desired service levels/SLAs? 3. (PEOPL
​The Problem: 
What is the true cost of escalating too many Tier 1/Level 1 tickets to Level 2/3 engineers?

Things to measure: How does this impact:1. (MONEY) Cost per incident - what does this cost the business? 2. (TIME) Service Level - how does this impact desired service levels/SLAs? 3. (PEOPLE) Agent utilization - how does this impact backlog? are we overworking engineers? Does this contribute to staff burnout?