We summarize the end-to-end of the core value chain as two cores, one is the end-to-end process and the business of the supply chain, and the other is the end-to-end and the business of product development. Each enterprise because of different types often have a focus on each of the two value chains. Production OEM companies do not have their own product development, then only the supply chain, high-tech research and development enterprises can sell products core technology and patents, do not do specific supply chain things. And more manufacturing-oriented enterprises are often 1 and 22 of an organic combination.
Again on enterprise architecture and Business architecture:
The enterprise architecture itself emphasizes business-driven it, business and it matching and convergence rather than two skins, where we can see the core of our focus on the processes, activities, data, organization, resources five aspects of the content. And every aspect basically involves two aspects of business and it, including business-to-it transformation and mapping.
Enterprise Architecture-Hierarchies and Dimensions:
The complete enterprise architecture includes two aspects of business architecture and information system architecture.
An enterprise architecture is a multi-view architecture that is composed of business architecture, information architecture, application architecture, and technology infrastructure. The traditional Zachman Enterprise Architecture framework is still more business-biased and data-free, and does not embody a particular understanding of business and it relationships. For the TOGAF framework, it really embodies the tight integration of business-driven it, business and it, especially the three levels of architecture, including business architecture, information system architecture and data architecture. and the information system architecture includes application architecture and data architecture.
Business process and Business architecture:
According to the TOGAF methodology, an important step after the establishment of a business vision is to work on the business architecture. The core of the business architecture is still the business process architecture, and the business case model is derived from the analysis of the business process architecture, and if the analysis of business data is concerned, the business data schema is derived.
Again on the business structure:
For the business architecture, it is still recommended that you download the IBM CBM Modular business Model whitepaper, which is easily searchable online. The understanding and analysis of the business can still see two important main lines, namely, business process analysis and business architecture analysis, both closely combined. Process Analysis general reference value chain analysis of ideas, from top to bottom, layered decomposition, and business structure analysis is more to rely on process analysis, process Analysis identification and discovery of business activities, identification and abstraction of the corresponding business components.
CBM Modular business model:
The idea of enterprise architecture is integrated into the software architecture, that is, the real work on the software architecture level is further integrated, which reduces the abstraction of the IT level from the actual business level in the system analysis process. Changing the traditional software architecture only takes into account the implementation level and the technical aspects of the problem. For the introduction of methods and specific content, or from the software architecture of some core content to talk about.
The introduction of enterprise architecture in software architecture design:
The information architecture generally has two modes, one is data-oriented architecture and one is process-oriented architecture. The focus of data-driven architecture is in the data center, BI Business intelligence and other building use more, focus on the data model and data quality, for the process-oriented architecture, SOA itself is the key method and technology, focus on end-to-end process integration, architecture adaptation to process changes. The two architectures do not have strict boundaries, but complement and supplement each other.
Information Architecture Model:
It planning and IT consulting
For it planning, the following are the main ideas: from business to technology, from process to it, to the core model of value chain analysis and optimization drive forward. The core process includes the current situation analysis, gap analysis, goal-making, blueprint planning, implementation planning, and several key steps. Current situation analysis includes business status and it status quo, according to enterprise strategy to put forward business objectives and development planning, analysis of the current situation and the gap between the objectives of the problem set (define it construction objectives), according to gaps and problems to give a blueprint, according to the goals and issues to decompose sub-goals and sub-issues and blueprint planning content, Multi-dimensional evaluation and determination of follow-up implementation planning to define the priority of IT system construction implementation. This is the general logic of it planning.
It planning core Analytics logic-finishing:
On the core logic of IT Planning analysis:
First, the business architecture is mapped to the cloud-based business model and process, first of all the business architecture is focused on business processes and business components, is for the subsequent identification of application architecture and data architecture services, focus or business. Cloud computing technology level, even if the cloud-based operation is a technology-level content rather than a real business, the analysis of partial operating business model and process eTOM model gives a good idea, can refer to the model of the next etom, its own ability and cloud computing itself to match the layered height
Cloud computing planning with TOGAF as a guide:
First look at the longitudinal, for the full life cycle of the telecom operator. If it is a traditional manufacturing enterprise which corresponds to the core value chain model, the front view is similar to the strategy, planning, product, product after the corresponding to the specific delivery and follow-up after-sales service environment. For operational enterprises, product-as-a-service, the user is not the product but the ability to provide products, so the operational aspects of the refinement, including operational support, implementation, protection and billing. To form the complete life cycle of telecom operators.
Turn around and see eTOM's process framework, horizontal for the supply chain, resources, services, products four layers. It can be said that the essence of the whole process framework is not the longitudinal life cycle, but the longitudinal life cycle is only an extension of the value chain analysis method. It lies in the horizontal stratification, decoupling and progressive relationship. The underlying supply chain is the bottom of the infrastructure support layer, which ultimately forms the value dimension of the asset.
Re-understanding of the eTOM process framework:
For the entry point of the architecture analysis, it is still recommended to start with end-to-end process analysis, refine to the end-to-end of the business domain, then refine to 3, 4-level processes, and finally refine to the bottom of the EPC flowchart. Processes to sub-processes, to business activities, and business activities are carried out by business documents and business entities. Business entities need to be pumped out for data-level data modeling and analysis. From the Y model in the Aris Enterprise Architecture analysis, you can see that the left side of the Y model is the business architecture, the right side is the process architecture, and the bottom level is sufficient for the EPC process. The entire analysis sequence is end-to-end process analysis to EPC, combining data modeling and analysis, and using crud matrix analysis to form a high-end business architecture from bottom-up abstraction of business components.
The core idea of Enterprise Architecture analysis:
The entire IT plan always revolves around business and it, including business process, business data, post organization and role, and business control system, while it includes application architecture, data architecture and model, technical architecture and platform, infrastructure construction. Business-driven it, end-to-end business processes eventually landed on the functionality of the application system, the business data eventually precipitated into the data model of the database, we talk about SOA is also business-driven it, business and it convergence, business architecture and application architecture itself, especially the proposed business components While the data architecture itself from the traditional conceptual model, the logical model, the physical model itself is the integration and unification of business data and information data.
On the thinking logic of it planning:
For IT consulting is mainly related to information technology, business, management of three aspects of knowledge. The enterprise architecture gives us a better knowledge of IT consulting architecture, business processes, data, systems, organizations and people. methods, tools and techniques. Whether it is from the enterprise value chain analysis, or from a variety of industry standard business model and data Standard Model, will eventually fall to the above content.
It Consulting-Caprice Records:
Reference models and frameworks for industry it planning, combined with it planning methodology and implementation, have re-organized the IT planning knowledge system. For the horizontal axis mainly consider the methodology and steps of it planning, including the reference model, research phase, variance analysis and matching, target architecture, implementation strategy and management control six aspects of the content; for the vertical axis includes IT infrastructure, business infrastructure, business processes, data, technology systems, application systems, Seven aspects of the integration architecture.
It planning knowledge system collation:
The process architecture is the basis of the foundation, the process is decomposed, the highest end of the process view will not reflect the process, more reflects the value chain thinking. The data schema is static, modeled from the perspective of the core data entity. The data entity should be extracted from the EPC. High-end application architectures and high-end process views correspond. Process-driven it, but matching and correspondence are more complex.
IT architecture planning:
Process-driven It planning consists of two levels of content. From the theoretical level, the introduction of Enterprise Architecture Management (EAM) concept, the establishment of a business process as the core architecture system, through the research of the architecture system to achieve enterprise IT planning, from a technical point of view, the program is composed of Aris software tools (process management platform), the application of Aris process modeling method, To realize the Model management of enterprise process, establish the enterprise's IT strategy, enterprise organization, IT infrastructure and IT management process modeling. Through the research of model relationship, the "dynamic" effective planning of enterprise it is realized. Process-driven It planning has a large advantage in the following aspects, the author will explore one by one.
Process-driven it effective dynamic planning:
Enterprise IT architecture is composed of data architecture, application architecture and technical architecture together. Among them, the data architecture is the core of enterprise IT architecture, because the enterprise business Operation status under the information system support is reflected by the data in the information system, and the data is an important resource of information system management. Therefore, when building enterprise IT architecture, the first consideration is to consider the data architecture support to the current business. The ideal enterprise IT architecture planning logic is data-driven, that is: first define the data schema according to the Business architecture analysis, and then according to the data schema and business functions to define the application architecture, and finally according to the definition of data architecture and data architecture to design the technical architecture.
It planning-data is at the heart of the core:
When it comes to smart enterprises, the simple point is still in the enterprise all kinds of information can be fully and quickly collected, the information can be highly shared and co-delivery, can be knowledge management level of information processing to create a valuable database of experts, to guide the continuous improvement of follow-up. The enterprise itself can be highly self-adapting and self-adjusting under the intelligent architecture and information technology to achieve a high degree of coordination and rapid response, in order to efficiently meet the various business objectives and realize the value of the enterprise. Specific or from the perceptual, can be coordinated and intelligent three aspects to talk about smart enterprise.
About Smart Enterprise:
Enterprise 2.0 itself fusion of traditional web2.0 and SNS core idea, Enterprise 2.0 itself fusion web3.0 core idea, Enterprise 2.0 itself is borderless and fusion idea, Enterprise 2.0 really integrate knowledge management into enterprise business objectives.
Another talk about the core logic of Enterprise 2.0:
It can be said that the formation of methodology must do two levels of abstraction, one is the abstract of the actual problem, one is the abstraction of the solution, so that the methodology has a more general applicability. But we note that when it comes to universal adaptability, the specific applicability is inevitably sacrificed. Methodologies are classes, and best practices are objects. The best practice is to solve the specific problem, and the combination of the specific method tool technology mentioned in the methodology is a practical verification of the methodology.
Methodologies and best practices:
Enterprise architecture, business architecture, data architecture
