Enter volumes based on transactions from all your applications based on the business process layer.  Actual transaction volumes recorded for your expense or revenue stream.  Example; how many applications are sponsored by engineering that allow CREATE and UPDATE of a supplier or customer.  Enter the number of transactions in the engineering variable.  The engineering group has no authority to create either a supplier or customer.  All organizations are allowed to submit a certain set of inputs for a super user group to review and then those super users create and update the master record.  

Food for thought, the difference between the records created by the super user group and the volume of created party management records is the opportunity to scale and protect the reputation of your client.  

Now lets do the same for every update to a party management record.  All changes to a supplier or customer could effect pricing and tax or duty fees and each must use the formal change management process with many changes needing to have an authorized representative from the supplier or customer.  Digital records are in need of key control designs.  These are monitored and reported to the SEC.  

BUSINESS ARCHITECTURE 

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.  

• Aligns to APQC Process Framework
• Aligns to Principles in ISO 9001, 26000 and 27001 

ENTERPRISE ARCHITECTURE 
Aligns Zachman Framework Enterprise and Business Architecture with Executive and Leaders from a business management level across any organization.  

A method in which to align and benchmark any organization or agency, with the system(s) logic required from Architects in Row 3, to enable Row 4 engineers who need to supply physics. 


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.  

• observe the work process without any work in process limitations (WIP Limits), 
• with process step specific WIP Limits* (work state WIP limits), 
• or you may want to see the impact of the Tameflow approach with Kanban Token and Replenishment Token 
• or see the impact of the Drum-Buffer-Rope** method. 

* Well know in (agile) Kanban

** Known in the physical world of factory production

The "Tameflow approach" using Kanban Token and Replenishment Token as well as the Drum-Buffer-Rope method take oth the Constraint (the weakest link of the work process) into consideration when pulling in new work items into the delivery "system". 

You can also simulate the effects of PUSH instead of PULL. 

Feel free to play around and recognize the different effects of work scheduling methods. 

If you have questions or feedback get in touch via twitter @swilluda

Look at the simulation as if you would look on a kanban board. 

The simulation mimics a "typical" software delivery process. 

From left to right you find the following ten process steps. 

- please adjust variables accordingly