Organization Blueprints Documentation
Knowing the status quo of the organizations has been always the first step of all organization development including business improvement or business redesign. Naturally, organizations that don’t know their status quo, or know it but didn’t document it, should do it many times for different projects. C4e does it based on enterprise architecture concepts. The architecture is normally attributed to the building architecture. As we need blueprints, building’s skeleton, facilities, view, internal architecture, etc to design houses and towers and the blueprints are the basis of buildings, we need the blueprints more in enterprise designs. Houses are the simplest type of the phenomena. However, organizations are the most complicated phenomena. Maybe, the human’s body is closer to the organizations. A physician can not recognize the disease without understanding the body’s components and their effects. Our maps and documentations try to play the role for organizational managers and advisors. A macro-view of the elements of the organizations and their relations.
- Agility in documenting and drawing blueprints
- Interoperability of the documentations based on the architecture of the processes
Architecture Repository Maintenance
After organizational documentations, the most important concern of the managers is to deploy and operationalize them between the individuals of the organization and maintenance of the designs by them. As it was stated, organizations are more dynamic than humans. So, unlike anatomy of the human body, their maps change frequently. And managers and advisors can not rely on documents and information that are not updated and accurate. However, if our organization is an organization with a certain mechanism, its life affects the architecture of its components. Therefore, to prevent the blueprints from being useless papers, we should ensure their maintenance and update. For this purpose, C4e has developed solutions that ensure the maintenance. Although deployment is rooted in organizational culture at one end and no consulter can not guarantee its success completely, we ensure that we help organizational employees and managers by using organizational behavior and presenting experiences of other customers and technological instruments in this path.
- PISHRAN organizational portal
- The experienced methodology of organizational development
Business Process Management (BPM)
BPM is a new field of organizational advisory like an umbrella over the sporadic methods of organizational improvement and development ranging from 6 sigma and lean production to business process reengineering (BPR) and administrative automation. According to the life cycle proposed by QUT University, the following steps are taken after identifying organizational processes and each one can be the title of an independent organizationl process.
Process discovery (or known as processes’ modeling): here, the current state of any process is recorded, usually as one or several current process models.
Process analysis. In this step, the problems of the current process are identified, recorded and determined using performance measures. The output of this stage is some classified problems. The problems are usually prioritized in terms of their effect and are sometimes prioritized in terms of the required attempt to solve them.
Process redesign (or known as process improvement). The purpose of this stage is to identify the changes in the process, helping the problems identified in the previous step and letting the organization achieve its performance aims.
Process implementation: in this stage, the required changes to move from the current process to the future process are implemented. Process implementation includes two aspects: management of organizational development and process automation. Organization development implies the activities required to change the performance of all participants in the process. On the other hand, process automation addresses the development and deployment of IT systems (or the developed version of IT systems) that support the future process.
Process monitoring: when a redesigned process is implemented, data are collected and analyzed to know how the process works in terms of its performance measures and goals. Obstacles, repeated errors and deviations of the behavior are identified and modifications are applied.
Enterprise Architecture (EA)
Enterprise architecture is a framework to describe, coordinate and align all activities and elements of organization to achieve the strategic purposes of the organization. Enterprise architecture can be presented by a series of related models and the architect is responsible for choosing different suitable models. EA originates from information system architecture, especially information architecture, and the architecture is continued in the organization. In fact,we face a kind of reengineering throughout the organization in terms of information systems that tries to improve the working processes of the organization by using the information technology. According to IEAF Iranian national organizational architecture cycle that adapts to Togaf cycle, the stages of formulating the organizational architecture as an evolutionary development cycle are as follows:
Architecture vision:It’s the beginning of the architecture formulation determining the purpose and perspective of an architecture cycle.
Architecture designs: in the subsequent phases of the enterprise architecture, architecture of data, application and architecture of technology infrastructure are formulated for as is state and to be state.
Transition plan: in this phase, using the gap analysis between the as is state and to be state, the roadmap of architecture application and migration to the desirable state is determined. The output of the phase that includes a portfolio of projects starts the next stage (architecture application).
Architecture governance: to deploy the architecture governance and make sure of architecture maintenance and development.
Requirement management: it can be revoked simultaneously in all architecture cycle and it is used to define and update the stakeholders’ requirements of the architecture.
Architecture maturity assessment: the level of organizational architecture maturity is measured based on some measures and the self-evaluation method. Architecture maturity is measured periodically and the comparison of the courses’ score shows the development of the organizational architecture program.
System Analysis & Design (SAD)
System analysis process known as the life cycle of the software production is one of the important subjects in a system production. It results in the design of our final product not only techically but also scientifically. For this purpose, different tools are developed by software professionals and our colleagues in the company master some of them and will use them during the following stages:
Planning: In this stage, requirements are determined based on the requests, the project’s objectives are determined and a document of the information is gathered finally.
Analysis: Based on the document obtained in the planning stage, the path is examined, lacks and dependencies are recognized and the likely problems are identified in the project and the conditions of the project are identified and the information is collected as a document.
Design: After examining both documents, the general objective, path, team and the required resources and the main framework of the project are designed.
Implementation: In this stage, test, installation, maintenance and support are followed based on the document designed in the poject design.