Some improvement ideas on Organizational Structure Modeling
In order to establish enterprise impact ect, key models include the organizational structure of the enterprise and the relationship between organizations established based on the organizational structure. It includes the following layers:
Top layer:
Organization chart
Layer 2
Relationship Model between organizational unit
Layer 3
Role Relationship Diagram in an organizational unit
These three-layer models have obvious hierarchical relationships, and the current modeling tools cannot express these relationships well. Using googleearth, I think it can be expressed in the same way.
For example, to open this model, the external view is the organizational structure, the deeper view is the relationship between organizational units, and the relationship between roles within organizational units.
In order to establish these relationships, we need to examine the business of the Organization. The business is initiated by the customer's needs. How can the Organization find the customer's needs, how to form orders, and how to develop projects to meet the customer's needs, how to deliver and track customer satisfaction.
This can be achieved through business processes. The second layer of the organizational structure is the business process between organizational units, it is how the role in an organizational unit writes the business process to complete a business.
OK, so we can implement the relationship between the business process and the Organization in a way similar to Google Earth, so it must be clear and easy to understand.
If we can further consider it, we can even start to simulate the operation of these processes, which is the scope of the workflow system.
In order to achieve the scope of the workflow, We need to model the business events and time events. Various control variables can also be simulated through this modeling.
It's really a good thing. Before it comes out, I 'd better use rose to paint it honestly.