TIM has to be stupidly simple, all of the complexity is embodied in the business process itself.
The primary interface for TIM is the Value Stream Mapper. It is within this logical map that you construct the living blueprint for the business.
The essential element of the Value Stream Map is the process, and the beauty of TIM is that a process can cover any business function at any scale.
TIM does not have a fixed structure for the operation of a business, but there is a single correct model. But the skill of representing your business process in TIM is transferable to building a robust business. i.e. learning the Transparent Process Language, is the same as learning to model your business.
TIM is the platform for modelling your business.
A given process model can change over time, with the seamless ability to step from one instance of the model to the next.
The Process Model grows both without and within the business. Aspects of the model equally die when they become redundant or superseded. At every instant, the present substantiated model configuration is recorded in the Process Lifetime Tree.
The Process Lifetime Tree is closely related to the Object Lifetime Tree. In fact, Object Lifetime Trees are the direct products of the Product Lifetime Tree. There can be many Process Lifetime Trees within a business, and they can seamlessly be bound together
for figure see 2.i
Instructions and Reports provide the basis of control for processes.
- Object Lifetime
- Signal Tracking
- Signal Processes
The most basic representation of a process is the object lifetime tracking
P: hash → …
A process has an object mapping, with intrinsic properties applied to objects. Extrinsic properties are recorded as intrinsic properties of documents.